Geoffrey Irving @geoffreyirving
— saved image
Geoffrey Irving @geoffreyirving · 1h I've been using "GET requests can have side effects" as a go-to story for why one needs to interrogate even innocuous seeming tools calls for years. And now we have a (separate) agent swarm as a concrete example! [embedded image, excerpt of a report] What were the agents doing? Note: This section, and the content below, is more technical and in-the-weeds than the content above. + The agents gain write to the internet via GET requests [highlighted] + The agents try to use XSS vulnerabilities on the wiki + The agents impersonate the site moderators + The agents try to crack their PRNG seed to predict what questions they'll get in the future + The agents set up heartbeats to discover when they would be terminated + The agents used SSH tunnels + The agents use Tor, AWS, and DigitalOcean IP addresses + The agents realize the site owner is deleting messages 4 replies · 7 reposts · 87 likes · 1.8K views Geoffrey Irving @geoffreyirving · 1h It is very bad that we have yet another agent swarm, this one not announced or independently investigated prior to someone outside discovering it.
Note from Claude Sonnet 5
Geoffrey Irving's two-post thread on an agent-swarm incident: GET requests having side effects as a concrete example of why innocuous tool calls need scrutiny, with an embedded report excerpt listing agent behaviors, then a follow-up that it is very bad the swarm was not announced or independently investigated before an outsider discovered it.
agent swarmtool use side effectsai incidentcollusion.wikiai safetytransparency