openai-admin-api-key

• trufflehog 3.97.4
• gitleaks 8.30.1
• trufflehog issue 4698 (admin-key request)
• Reference 1
• Reference 2
• Reference 3
• Reference 4

Arrival evidence (#384, product redact-secret#863; research #777). T2: no OpenAI documentation states a length or alphabet for sk-admin- keys. Gitleaks corroborates the marker-bearing 58 + T3BlbkFJ + 58 shape with three test vectors, trufflehog 3.97.4 matches exactly that shape in its dedicated openaiadmin detector (PR #4689, which is why the generic openai detector skips sk-admin-: a move, not an exclusion; corrected by redact-secret#1013), and openai/codex fixes the prefix set and the T3BlbkFJ watermark for the OpenAI family. The product decision recorded in redact-secret#863 contracts sk-admin- under the same marker-gated 58/74-byte grammar as sk-proj- and sk-svcacct-, so the shipped detector admits 58/58 and 74/74 and no mixed width. The benchmark claim is 58/58 only (redact-secret#1013): no source anywhere shows a 74/74 admin value, so 74/74 is outside the claim and no fixture asserts it either way, while the product keeps accepting it (security-first). No source shows a 74/74 admin value: only the gitleaks union shared with sk-proj-/sk-svcacct- admits it, while trufflehog openaiadmin, nuclei-templates and poltergeist admit 58/58 only (redact-secret#1013 recommends taking 74/74 out of the positive set). A marker-less sk-admin- body (the 124-character trufflehog request) is out of contract: no source shows such a key, so it is authored as a negative twin, and the product accepts a false negative for it when bare or in unquoted env, YAML or tool-call text.