Agent Name Collision Attacks in Multi-Agent Systems
A multi-agent system vulnerability is identified where remote names are used as routing identifiers, causing wrong-peer dispatch.
This research paper describes an Agent Name Collision Attack in Multi-Agent Systems, where remote names are used as routing identifiers, causing wrong-peer dispatch.
- Multi-agent hosts use remote names as routing identifiers, causing wrong-peer dispatch
- Products
- Gemma agent
- Threat actors
- adversaries
- Malware
- LockBit
- Organizations
- Microsoft
- Countries
- European
- AI models
- GPT-oss-20b
From the original article
1 min read at arxiv.orgMulti-agent hosts turn remote Agent Cards into local agents, tools, workflow targets, and broker routes. A2A defines the card's name as human-readable metadata, not as a stable identity, and specifies no collision semantics. The security failure begins when a host nevertheless uses that remote name as a local routing identifier.
By Adithyan Arun Kumar · arxiv.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.