Notifications
Clear all
Topic starter
06/09/2026 6:21 pm
TL;DR: AI systems can be hijacked when exposed to non-human identity secrets, with attackers attempting access to public AWS credentials in an average of 17 minutes and as quickly as 9 minutes, according to Reco AI. The security problem is not prompt content alone but the trust and privilege context wrapped around it, which makes credential governance central to AI risk reduction.
NHIMG editorial — based on content published by Reco AI: LLMjacking: How Attackers Hijack AI Using Compromised NHIs
By the numbers:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes.
Questions worth separating out
Q: How should security teams handle exposed secrets in AI-driven environments?
A: Security teams should treat exposed secrets as active access paths and respond as though misuse can begin immediately.
Q: Why do compromised NHIs create extra risk for AI workflows?
A: Because AI workflows often rely on delegated credentials to retrieve data, call tools, or trigger automation.
Q: What signs show that AI-connected credentials are being abused?
A: Look for unusual request sources, unexpected API call volume, connector activity outside normal schedules, and access to data sets the identity does not usually touch.
Practitioner guidance
- Map every AI-connected non-human identity Identify the service accounts, API keys, OAuth tokens, and cloud credentials that can reach AI systems, then classify them by privilege, lifespan, and revocation path.
- Reduce credential replay windows Move exposed or high-risk AI credentials to short-lived tokens, enforce rotation on a defined cadence, and automate revocation when secrets are discovered outside approved storage.
- Scope tool and retrieval permissions separately Review the permissions that let the model call tools, read data, and inherit session context, then remove access that is not required for the specific workflow.
What's in the full article
Reco AI's full article covers the operational detail this post intentionally leaves for the source:
- The article's example-based discussion of how compromised NHIs can be used to hijack AI workflows through exposed credentials.
- The specific attacker behaviour patterns observed around public AWS credentials and AI-linked secret exposure.
- The source's broader context on why prompt risk is secondary to credential and privilege context.
- The vendor's supporting examples of real-world exposure scenarios that help teams operationalise detection and response.
👉 Read Reco AI's analysis of LLMjacking and compromised NHI secrets →
LLMjacking and compromised NHI secrets: what practitioners should watch?
Explore further
06/09/2026 6:21 pm
Compromised NHI secrets are now an AI control-plane problem. When credentials, tokens, and service accounts sit behind AI workflows, the attacker does not need model access in the abstract. They need the same machine identity trust path that the workflow already uses. That means AI governance and NHI governance are now inseparable at the point of execution, not just at policy design. Practitioners should treat AI-connected secrets as control-plane assets, not implementation details.
A few things that frame the scale:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes, according to LLMjacking: How Attackers Hijack AI Using Compromised NHIs.
- Exposure can become exploitation in as little as 9 minutes, according to the same Entro Security research, which leaves very little room for manual review.
A question worth separating out:
Q: How do IAM and PAM teams split responsibility for AI agent access?
A: IAM should define what the agent can reach, while PAM should control when elevated access is available and how it is revoked. For AI agents, those responsibilities must be coordinated because programmatic identities do not fit a human session model. If scope and elevation are managed separately without a shared lifecycle view, privilege can persist longer than anyone expects.
👉 Read our full editorial: LLMjacking shows how exposed NHI secrets can hijack AI systems
