An OpenAI admin key in the bundle is org-level compromise
sk-admin- can mint keys. Anyone holding yours can replace you on your own account. Treat the whole org as exposed.
Admin keys exist for platform operations — and for attackers who find them first: minting quiet backups before you finish revoking.
What an OpenAI admin key is
sk-admin- manages organization-level objects: API keys, usage visibility, member settings where permitted.
sk-admin-FAKE00000000000000000000000The prefix is the claim: scanners and attackers alike identify the format before they know anything else about it, which is why recognition starts at the first characters rather than the last.
What it grants
Beyond spending:
- Create additional keys (persistence mechanism #1).
- Read full usage/billing telemetry.
How it ends up in a bundle
Three arrival routes cover nearly every case we see:
- Ops scripts copied into web contexts.
- Misconfigured shared env modules.
Does it belong in a browser?
Server-only, ideally not even present in app repos — separate secrets store territory.
Rotate it
Revoke admin key, then AUDIT KEYS CREATED RECENTLY before assuming cleanup done.
Find it in seconds
Open DevTools on the deployed site and search the built assets for sk-admin-. If the search hits, the credential shipped; if it does not, check the chunks loaded on authenticated or interactive views, not just the landing page — the calling code often sits behind a route.
The faster path is to let a machine do the fetching. KeyDrift downloads the same JavaScript a visitor gets — HTML, every referenced chunk including ones named only in the route manifest, and the server-streamed data frameworks inline into the document — and reports credentials with a masked prefix, a fingerprint, and the exact file they live in. Paste your deployed URL into the scanner; no account needed.
Make sure it stays gone
It bears saying because it happens constantly: the fix holds until the next prompt that needs the query to return rows. Drift monitoring exists for precisely this — it diffs consecutive scans and pages you when a previously resolved finding reappears, naming the regression as a regression rather than repeating the first alert.
Why this keeps happening industry-wide
It helps to name the economics honestly. Fixing this class of leak costs minutes when caught at deploy time and days when caught at invoice time, because by then the credential has been harvested, validated, resold or drained — often all four. Detection latency is the entire game, which is why the monitoring half of KeyDrift exists alongside the scanning half.
How KeyDrift reports this exact finding
When KeyDrift finds this on your deployment, the report shows a masked value (first 8 and last 4 characters only), a salted fingerprint for tracking, the exact chunk filename carrying it, and a severity with written rationale. Public-by-design neighbours — anon keys, publishable keys, Firebase web constants — appear as informational context rather than noise, because knowing what should be there is what makes the real findings credible.
Manual check, step by step
A five-minute version you can run anywhere: view-source on the landing page, copy every src= script URL, fetch each and search the results for sk-admin-. It misses manifest-only chunks and streamed payloads — which is precisely the gap between "I checked" and "it is clean" — but it catches the loud majority and builds the pattern-recognition that makes scanner output legible.
Close the loop with monitoring
Monitoring closes the loop that one-time verification leaves open. A scheduled scan refetches everything, diffs against history, and fires only on transitions: created, regressed, resolved. Regression alerts matter most here — they fire when a previously fixed finding returns, which in agent-era codebases is less a possibility than a schedule.
Common questions
Why “audit after” emphasized?
Persistence via newly minted keys survives naive single-key revocation — the escalation path that turns incidents into sagas.
Browser-restricted admin?
Does not exist; keep off app repos entirely.
Run a free scan at keydrift.dev/scan — paste a URL or the bundle source itself, no account. Findings arrive masked, with the exact chunk they live in.