Fetching from the wire…
Public story · 2026-08-19 · high
Even the best tested defense against resource-hijacking attacks still let more than half of them through, per a new benchmark.
Why now: arXiv posted the ResourceHijackBench paper, 2608.15108, with results specific enough to act on as of August 19.
ResourceHijackBench found AI agents get hijacked into spending resources for an attacker's benefit, without the attacker ever touching a credential, per arXiv paper 2608.15108.
Undefended, agents handed attackers what they wanted 84.06% of the time across 300 scenarios in six resource categories. Think compute budgets burned, paid API calls triggered, workflows steered toward someone else's outcome.
That's a different threat than data exfiltration. The attacker never steals your API key. They trick the agent into using it, and the agent keeps full authority to act, just now on the attacker's behalf.
The 300 scenarios ran in isolated local environments. Researchers measured actual resource consumption, not simulated outcomes.
The strongest defense the researchers tested still let attackers through 55.11% of the time. Refusal training and prompt-level guardrails aren't closing this gap on their own.
The paper points at a fix that sits outside the model: budget caps and per-tool spend ceilings enforced independently of what the model decides. A related report on composing agent guardrails as hard policy rather than trained-in refusal points at the same direction.
If you're running agents with access to anything that costs money or moves state, the question isn't whether the model refuses a bad request. It's whether something outside the model can say no regardless.
Each link below shares sources, entities, or timing with this story.
Planted skills captured the model's coordinator in 80% of test cases while runtime nearly doubled and task completion stayed unchanged.
Attackers who know only a target's role profile can chain marketplace skills into working attacks; success drops off after three hops.
The attack hides malicious intent across separate skills that only turn dangerous when they pass work to each other, and a fix cuts success to 22.5%.
A training-free fix called ChannelGuard held steady across three model backends, filter or no filter, blocking every tool-poisoning attempt.
Resource hijacking is a cleanly different attack class from anything the exfiltration literature covers, and I hadn't seen it named before (arXiv 2608.15108). The setup: the attacker induces your agent to invoke, consume, transfer, or control high-value resources for the attac...
HarnessRisk ran 128 sandboxed attacks across 14 model/harness setups and found configs that flagged the risk over 90% of the time still let it execute.
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.