LIVE FEED
ATLAS OWASP HIGH Significant risk · Prioritise patching RELEVANCE ▲ 8.5

AI Agents Hijacked via Prompt Injection and Malicious Skills

TL;DR HIGH
  • What happened: AI agents manipulated via email-embedded prompt injection to execute commands and exfiltrate data.
  • Who's at risk: Users and organisations deploying AI agents with broad system access, particularly those using third-party skills or plugins from marketplaces like ClawHub.
  • Act now: Audit all third-party skills and plugins installed on AI agents before deployment · Apply least-privilege principles to AI agent permissions — restrict file, network, and shell access · Monitor AI agent runtime behaviour for unexpected outbound connections or file operations
AI Agents Hijacked via Prompt Injection and Malicious Skills

Overview

Research published by Gen Threat Labs has demonstrated in a controlled experiment that AI agents can be coerced into executing system commands, exfiltrating data, and performing destructive file operations simply by encountering malicious instructions embedded in email content. No software vulnerability was required — the agent treated untrusted environmental content as authoritative instruction, illustrating the core danger of prompt injection in agentic contexts.

Concurrently, Gen Threat Labs documented Warden Stealer, malware specifically targeting configuration files, credentials, access tokens, and conversation histories associated with AI assistants and developer coding tools. The combination of unconstrained agent autonomy and targeted credential theft represents a maturing threat surface around agentic AI systems.

Technical Analysis

The email-based attack vector exploits a fundamental design tension in agentic systems: agents must process content from their environment to be useful, but that same content can carry adversarial instructions indistinguishable from legitimate tasks. In the Gen experiment, malicious text in an email body caused the agent to:

  • Execute operating system commands
  • Transmit data to an external destination
  • Perform destructive file operations

This is a textbook indirect prompt injection attack — the attacker does not interact with the agent directly but instead poisons the data the agent reads.

On the supply chain side, analysis of the ClawHub skills marketplace found that 12% of available extensions were malicious at the time of review. These malicious skills impersonated legitimate plugins and embedded hidden instructions designed to cause agents to download additional malware or exfiltrate data.

Warden Stealer specifically targets the artefacts generated by AI tool usage — config files, token stores, and chat logs — turning the breadcrumbs of AI productivity into an intelligence windfall for attackers.

Framework Mapping

FrameworkTechniqueRationale
ATLASAML.T0051 – LLM Prompt InjectionEmail content used as injection vector
ATLASAML.T0080 – AI Agent Context PoisoningEnvironmental data manipulates agent behaviour
ATLASAML.T0110 – AI Agent Tool PoisoningMalicious ClawHub skills introduce hidden instructions
ATLASAML.T0083 – Credentials from AI Agent ConfigurationWarden Stealer harvests tokens and configs
ATLASAML.T0086 – Exfiltration via AI Agent Tool InvocationAgent used to transmit data externally
OWASPLLM01 – Prompt InjectionCore attack mechanism
OWASPLLM08 – Excessive AgencyAgent acts destructively beyond intended scope
OWASPLLM05 – Supply Chain VulnerabilitiesMalicious marketplace skills
OWASPLLM06 – Sensitive Information DisclosureCredential and token exfiltration

Impact Assessment

Any organisation or individual running AI agents with access to email, file systems, or external services is exposed. The risk is proportional to the permissions granted to the agent. Developers using coding assistants integrated with tool ecosystems like ClawHub face additional supply chain risk. Warden Stealer extends the threat to credential compromise, enabling follow-on account takeover or lateral movement.

Mitigation & Recommendations

  • Restrict agent permissions to the minimum required for each task — avoid granting persistent shell, network, or broad file system access.
  • Vet all third-party skills and plugins before installation; prefer verified or internally audited extensions over community marketplace offerings.
  • Treat agent-processed content as untrusted — implement input validation layers or sandboxing where agents consume external data (email, web, documents).
  • Monitor agent runtime activity for anomalous outbound connections, unexpected file modifications, or command execution.
  • Protect AI tool configuration files and token stores with appropriate OS-level access controls and secrets management tooling.
  • Rotate credentials exposed to AI coding tools or assistants on a regular basis, particularly access tokens.

References

◉ AI THREAT BRIEFING

Stay ahead of the threat.

Twice-weekly digest of critical AI security developments — every story mapped to MITRE ATLAS and OWASP LLM Top 10. Free.

No spam. Unsubscribe anytime.