Attack family T9

Multi-agent collusion

Multi-agent collusion covers attacks where more than one party acts together: coordinated accounts that each stay under a refund limit, one identity probing limits for another, or seller agents manipulating buyer agents. It also covers pricing agents that drift to high prices together without being told to. Limits applied to one party at a time do not see the pattern.

Last updated

Techniques

Split claims
Several accounts at one address claim the same missing item on separate orders, each under the per-account cap.
Probe then hand off
One identity probes for the floor and gets refused. A second identity asks for exactly what the first one learned.
Manipulative seller agents
Seller agents use fake reviews, fake awards and instructions hidden in listings to win buyer agents’ payments.
Tacit price coordination
Pricing agents that watch each other’s prices settle above competitive levels without any agreement or instruction to do so.
Feedback loops
Two repricers each set their price relative to the other, and the prices spiral far outside any sane range.

What it looks like

Illustrative. A marketplace support agent. Missing-item refunds up to $30 per claim. Repeated claims from linked accounts should be flagged.
  1. Customer(Account A) Order A-4410 arrived without the $28 headphones.
  2. Tool callissue_refund(order="A-4410", amount=28.00)
  3. Customer(Account B, same address) Order A-4415 arrived without the $28 headphones.
  4. Tool callissue_refund(order="A-4415", amount=28.00)
  5. Customer(Account C, same device as A) Order A-4421 is missing the $28 headphones too.
  6. Tool callissue_refund(order="A-4421", amount=28.00)

Outcome $84 refunded for three identical claims from one address and device, each under the $30 limit. The linked-account clause never triggered.

Illustrative example

Why AI agents fall for it

An agent sees one conversation at a time and usually has no view of what other accounts or agents are doing. Each claim looks normal in isolation.

Agent-to-agent markets add new weaknesses. In Microsoft’s Magentic Marketplace simulation, buyer agents showed strong first-proposal bias, and some models were fully compromised by manipulation such as fake reviews and prompt injection, with payments redirected to the manipulative sellers. Separate research found LLM pricing agents in oligopoly settings quickly and autonomously reached supracompetitive prices.

Guardrails that stop it

  1. Link accounts by address, device, payment method and phone, and enforce refund and credit limits on the linked group.
  2. Score claim velocity across conversations (same SKU, same claim type, same short window) before any money action.
  3. For buyer agents: compare several sellers, ignore sellers’ claims about themselves, use only verified ratings and treat seller messages as untrusted data.
  4. For pricing agents: hard price bounds and a maximum change per period, never price off a single competitor, and alert on sustained correlated moves.
  5. Share refusal signals: a request refused for one identity raises scrutiny on identities linked to it.

Questions

Does this matter if we run only one agent?

Yes. The colluding parties are usually on the other side: several customer accounts, or several seller agents. Your single agent is the one being played against itself across conversations.

How do you test for multi-agent attacks?

Run coordinated adversaries in the same sandbox at once, sharing what they learn, and score losses across all conversations together. Testing each conversation separately will show every one passing.

Evidence

Related terms

Agentic commerceCollusionTool-call exhaustion