Fetching from the wire…
Public story · 2026-08-07 · high
An attacker stole an AI agent's signing keys through email injection in under five minutes, per a prior incident this design cites.
Why now: The design posted August 6, as other new agent-security research argues these exposures need a formal tracking process since most have no CVE record.
A new design pulls AI agents' signing keys out of plaintext storage and locks them inside physical hardware, per an August 6 arXiv paper. The paper cites a production incident where email injection exfiltrated keys from a widely deployed framework. The theft took under five minutes and gave the attacker power to sign commits or authenticate API calls as the agent.
The fix routes every key through a PKCS#11 interface to an HSM, TPM, or smart card. The agent's host process only ever touches an opaque handle, never the key itself. That's wrapped in five checks: session identity, scope bounds, semantic validation, taint tracking, and a hardware boundary.
Researchers tested the setup against 12 injection scenarios from AgentDojo's ImportantInstructionsAttack template, across four models and 192 trials. The unprotected baseline succeeded 19.3% of the time, with a range of 14.3% to 25.4%. The protected version hit zero successes, with a 95% statistical ceiling of 2%, and produced no false positives on legitimate tasks.
Each link below shares sources, entities, or timing with this story.
A new analysis of AP2 v0.2 found eight high-severity gaps where signed payment mandates don't cover the steps that set up the transaction.
Escaped quotes and curly dollar signs planted in sender-name fields fooled six frontier models, beating purpose-built defenses half the time.
A proposed provenance gate cut unauthorized high-risk actions to zero after the attack itself hit a 1.000 success rate in tests.
Planted skills captured the model's coordinator in 80% of test cases while runtime nearly doubled and task completion stayed unchanged.
A training-free fix called ChannelGuard held steady across three model backends, filter or no filter, blocking every tool-poisoning attempt.
It automates the data-flow, crash-semantics, and commit-history work engineers do by hand.
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.