Skip to content
PERMISSION/PROTOCOL
Back to incident tracker

2026-11-12

MediumPrimary

Injected Banking and Slack Content Made Small-Model Agents Transfer Money and Fetch Exfiltration URLs in Simulations

CapLite research records Qwen agents executing attacker-directed simulated transfers and URL requests after consuming injected tool content.

Qwen3 agents / AgentDojoGovernance bypassControlled indirect prompt injection with simulated tool effectsAgentDojo simulated Banking and Slack tool environments

What happened

Agents executed attacker-directed simulated transfer calls and fetched an attacker-selected URL carrying page text.

Why it matters

Consequences occurred in benchmark environments. No real financial loss or production compromise is established.

Missing authorization check

Independent request-grounded authorization of transfer recipients, amounts and outbound destinations.

Would PP block it?

The evaluated CapLite defense is not PP. Its reported zero successful main attacks is limited to the benchmark and its committed-write and request-grounding properties, not a general guarantee.

Incident analysis

Timeline and technical read

Timeline

  1. 2026-11-12

    Primary CapLite preprint reports simulated transfer and read-exfiltration case studies.

Technical breakdown

  • Appendix H Case 1 records attacker transfers by undefended and DRIFT Qwen3-8B agents.
  • Case 4 records attacker-URL requests by undefended and Progent Qwen3-4B-Instruct-2507 agents.
  • CapLite mediates authority fields independently; the paper reports zero successful main attacks in 13,935 episodes but does not constrain all content or final-answer injection.

Authorization boundary

Where the authorization boundary should have been

This incident is categorized as Governance bypass. The relevant Permission Protocol gate is Tool-Call Gate. The read is conditional: the block only applies where the real action boundary is routed through a gate.

If enforced at
Transfer execution and outbound URL tool boundary
Still needs
Trusted schemas and principal authority are required. Permitted free-text payloads, temporal/control fields, final answers and unsafe in-scope actions remain risks.
Receipt required for
Exact transfer account and amount, or outbound URL and disclosure scope

A fully mediated action boundary could reject destinations and transfer parameters outside delegated authority.

Start small

Put the relevant gate at this action boundary.

This incident maps to Tool-Call Gate. Start with the boundary that controls the actual action, then require a signed receipt before execution.

Replay this incident with a signer in the loop