TL;DR: Truffle Security's analysis of model distillation finds a stolen API key can let attackers harvest responses, burn quota, and shift costs onto the victim. Secret revocation and ownership need to be treated as billing controls as well as access controls.
Editorial analysis by NHI Mgmt Group, based on content published by Truffle Security: “Model Distillation: Why Attackers Want Your API Keys”.
By the numbers:
- OpenCode disclosed a breach affecting 1.4% of its Console users.
Key questions
Q: Why do leaked model API keys create financial risk as well as access risk?
A: Because each request can consume paid capacity under the victim’s account.
Q: How do organisations know if their AI governance is too weak?
A: Weak AI governance shows up when legitimate accounts can create harmful content, export it repeatedly, and feed it into other systems without raising scrutiny.
Q: What breaks when an API key is stolen in a model platform?
A: The key stops being a simple authenticator and becomes a funded abuse path.
Practitioner guidance
- Inventory spend-bearing API keys Classify every model-facing key by owner, billing impact, provider, and revocation path so teams can prioritise the secrets that can generate direct cost if abused.
- Revoke keys through provider controls first Use the provider-side revocation path as the containment step, then validate that downstream gateways, proxies, and mirrors can no longer replay the credential.
- Audit intermediary retention of secrets Review coding assistants, gateways, ticketing tools, and prompt logs for any place a live credential can be stored, replayed, or copied into training workflows.
Bottom line: A stolen model API key can function as both an access credential and a cost-bearing resource, which makes compromise financially as well as operationally damaging.
Glossary terms: Model Distillation, Spend-Bearing API Key, Credential Retention Boundary
What's in the full article
Truffle Security's full blog post covers the operational detail this post intentionally leaves for the source:
- Provider-by-provider discussion of published monthly spend limits and how they affect abuse potential
- Explanation of why alerts, hard limits, and billing delay do not stop all malicious requests at once
- Examples of how coding assistants and retained transcripts can carry live secrets into downstream workflows
- Context on TruffleHog detection and verification workflow for exposed credentials
👉 Read Truffle Security's analysis of model distillation abuse and API key risk →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
API keys have become spend-bearing identities, not just access tokens: In model ecosystems, a stolen key can finance the attack itself because each request converts into billable output and training data. That changes how identity teams should think about blast radius. The risk is no longer limited to unauthorized access. It includes a direct transfer of compute cost and account capacity to an attacker, which means key governance is now a financial-control issue as well as an authentication issue.
A few things that frame the scale:
- DeepSeek alone generated 113,000 new exposed API keys in 2025, illustrating how new AI providers create credential exposure before security guardrails catch up, according to the State of Secrets Sprawl 2026.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should organisations do when intermediaries store or forward API keys?
A: Treat the intermediary as part of the credential boundary and require lifecycle controls over storage, logs, backups, and offboarding. If the service can replay the secret, it can also prolong exposure. That means procurement, engineering, and security all share responsibility for where the key can persist.
👉 Read our full editorial: Leaked API keys can fund model distillation and charge victims