{"version":"2.1.280","anchor":"forgedinjected-teammate-messages-are-now-flagged-unverified","canonical_anchor":"forgedinjected-teammate-messages-are-now-flagged-unverified","heading":"Forged\/injected teammate messages are now flagged unverified in the swarm transcript format","tier":"notice","area":"Teammates","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/forgedinjected-teammate-messages-are-now-flagged-unverified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Forged\/injected teammate messages are now flagged unverified in the swarm transcript format\n\nClaude Code now marks forged or injected teammate messages as unverified in swarm transcripts\n\n**Unclear.** The finding does not say how a message's provenance comes to be judged 'forged' in practice.\n\n**What**\n\nIn Claude Code's swarm mode, where multiple Claude instances (teammates) work together and exchange messages, the transcript format now tracks whether a message's origin can be trusted. A teammate message can be tagged `verified=\"false\"` when its provenance is judged 'forged' (meaning it looks like it came from a teammate but its origin is suspect).\n\nWhen a message is marked this way:\n\n- its content is no longer scanned for mentions or tool names\n\n- the sender's name is shown with an `(unverified)` label next to it\n\n**Why**\n\nThis makes it easier to spot a message that was injected or spoofed to look like it came from a legitimate teammate, rather than having it silently treated the same as a genuine message.\n\n- Area: Teammates\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}