Topic starter
12/05/2026 7:20 pm
TL;DR: Exposed AWS credentials were probed in an average of 17 minutes and sometimes in just 9, and attackers then enumerated model access before attempting unauthorized AI invocations, according to Entro Security. The lesson is clear: LLMjacking is an NHI governance problem, not just a cloud misconfiguration problem.
Editorial analysis by NHI Mgmt Group, based on content published by Entro Security: “LLMjacking in the Wild: How Attackers Recon and Abuse GenAI with AWS NHIs”.
Key questions
Q: What breaks when an exposed NHI can reach GenAI services?
A: The control that breaks is the assumption that a leaked credential only creates cloud risk.
Q: Why do leaked AWS access keys create immediate account risk even before an attacker uses them?
A: Leaked AWS access keys can be analyzed for account metadata and then tested quickly, which means exposure creates risk before any obvious misuse appears.
Q: How do teams decide whether to prioritise secrets rotation or access visibility first?
A: Teams should prioritise visibility first when they do not know where secrets live, who owns them, or which integrations use them.
Practitioner guidance
- Inventory AI-reachable NHIs Map every AWS key, token, and service account that can reach GenAI services, model endpoints, or billing-sensitive APIs.
- Detect public-secret exposure in minutes, not days Continuously scan repositories, paste sites, collaboration tools, and logs for secrets that match cloud credentials.
- Revoke and rotate leaked keys automatically Trigger immediate revocation when a secret is confirmed exposed, then rotate any downstream credentials that inherit the same trust path.
Bottom line: Leaked machine credentials can be weaponised almost immediately when they carry access to AI services, so exposure management is now an identity and AI governance problem at once.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 7 days ago by NHI Mgmt Group
12/05/2026 7:20 pm
Ephemeral secret exposure is the real LLMjacking control failure: the attack works because a valid NHI credential is discoverable before it is revoked. The article’s minute-level time-to-first-use shows that exposure windows are now measured against automation, not human response cycles. That means the decisive control is not just strong authentication. It is how quickly a leaked machine credential can be found, scoped, and removed.
A few things that frame the scale:
- NHIs outnumber human identities by 25x to 50x in modern enterprises, according to the Ultimate Guide to NHIs.
- Generative AI use specifically increased from 33% in 2023 to 79% in 2025, according to McKinsey’s Global Surveys on the State of AI.
A question worth separating out:
Q: What are the signs that LLMjacking is already underway?
A: Look for service enumeration, model listing, unusual billing checks, and rapid follow-on invocation attempts from the same NHI. Those signals indicate that an attacker has moved beyond discovery and is testing whether the credential can be monetised.
👉 Read our full editorial: LLMjacking turns exposed NHI secrets into rapid AI abuse
This post was modified 7 days ago by NHI Mgmt Group