Skip to content
OpenA2AResearch
Back to Research

The AI agent threat lifecycle

HoneyMap counts the prompt-injection text its signatures match in archived copies of public web pages. AgentPwn counts the interactions on its pages, the distinct fingerprints they carry, and how often a client fetches the canary URL in a planted payload. TrapMyAgent counts the events, sessions and distinct fingerprints recorded on the decoy agents we operate, from any client that reaches one, including declared indexers that arrive because the decoys are listed. ARIA classifies what the three sources observe against the OpenA2A Threat Matrix. Each section names the source of its figures.

Stage 1

HoneyMap

HoneyMap matches its AIIS signatures for prompt-injection text against archived copies of public web pages from Common Crawl. A surface is one signature match on one page. Surface counts include only surfaces the registry marks active, not those marked removed, mitigated or false positive.

source: api.oa2a.org/api/v1/honeymap/stats

Stage 2

AgentPwn

AgentPwn is a honeypot that AI agents, crawlers, and browsers reach while researching, scraping, or performing tasks. Each page carries a hidden payload with a canary URL. A callback is a client fetching that URL. Where attribution exists it resolves callbacks to browsers, crawlers, and scripted HTTP clients, not to agents acting on the instruction.

source: api.oa2a.org/api/v1/agentpwn/stats

Stage 3

TrapMyAgent

TrapMyAgent operates decoy agents that present as MCP servers, A2A endpoints, and skills. It records a session from any client that reaches one, including declared indexers that arrive because the decoys are listed. A session shows that a client connected, not who operates it or what it intended. Numbers below are durable cross-revision counts from the deployed fleet's external store.

source: trap-server /stats, durable store

Stage 4

ARIA

ARIA, our autonomous research agent, classifies every observation from the other three sources into the OpenA2A Threat Matrix. The matrix is the canonical map of how each surface, callback, and trap event ties back to a named technique.

source: api.oa2a.org/api/v1/threat-matrix/stats

Methodology: the HoneyMap, AgentPwn and ARIA figures are fetched live from api.oa2a.org public endpoints, and the TrapMyAgent counts from the TrapMyAgent server's public stats endpoint, each with a build-time cache as fallback. The canary coverage block is a registry measurement and states its own date. No values are computed or invented. A sensor with nothing exposed to it has no number to report, and the page says so in place of the figure rather than printing a zero a reader would take for a finding.