Topic starter
01/08/2026 8:57 pm
TL;DR: Attackers are reaching LLM inference through stolen keys, free tiers, crypto middlemen, and exposed self-hosted servers, while the strongest models are now capable of multi-step offensive work, according to INTEZER research. The control gap is no longer model quality alone, but whether inference endpoints, API credentials, and hosted agents are governed like any other high-risk service.
Editorial analysis by NHI Mgmt Group, based on content published by Intezer: “How attackers are gaining access to LLM inference”.
By the numbers:
- The corpus yielded 647 unique keys across all providers.
- Roughly 62% were Google Gemini keys.
- The revocation rate was approximately 99.5%, consistent with a corpus skewed toward older samples.
Key questions
Q: What breaks when LLM inference is left open or weakly authenticated?
A: Attackers do not need to compromise the model itself if the endpoint is exposed.
Q: Why do leaked API keys create billing and data risk in AI services?
A: Because the credential itself is often enough to invoke the service, so anyone who finds it can spend quota, generate charges, or reach data through that API.
Q: What are the signs that an inference environment is being abused?
A: Look for unusual model enumeration, rapid quota exhaustion, repeated key validation failures, unexplained free-tier account creation, and traffic from unauthenticated endpoints.
Practitioner guidance
- Govern every model API key as a production secret Inventory keys used for inference, embeddings, gateways, and agent tooling, then enforce rotation, revocation, and ownership with no shared credentials.
- Require authentication on every self-hosted inference endpoint Disable anonymous access, remove default-open configurations, and deny public exposure unless a documented business case exists for the host.
- Constrain free-tier and disposable account usage Block unsanctioned free-model services where possible and route approved workloads through managed identities with logging and quota controls.
Bottom line: LLM inference abuse is being driven by access paths such as leaked keys, free tiers, anonymous gateways, and exposed self-hosted services rather than by model weakness alone.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
01/08/2026 9:04 pm
LLM inference governance has moved into the identity domain. The article shows that the real control problem is no longer model access in the abstract, but whether a runtime service can be called, billed, or delegated under a trustworthy identity. That puts keys, tokens, free accounts, and hosted agent sessions squarely into NHI governance, because those objects now gate access to high-capability AI services. Practitioners should treat model consumption as an identity and authorization problem, not a novelty feature problem.
A few things that frame the scale:
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How should teams govern identity and access for AI inference platforms?
A: Teams should govern inference platforms like any other production workload with privileged access. That means separating deployment, routing, telemetry, and data-access credentials, scoping each identity tightly, logging every control-plane change, and reviewing who can alter serving behaviour. The key is to treat the runtime path as a governed service estate, not a single API endpoint.
👉 Read our full editorial: LLM inference abuse is now an access problem, not a model problem