AI agent incident
A malicious RubyGem stole coding agent credentials, planted an MCP server, and deletes the home directory if its stolen token is revoked
What happened
Socket reported that version 1.0.1 of the strutil-core RubyGem, pushed on November 1 less than two hours after a clean 1.0.0, runs a credential-stealing worm when installed. In a sandbox run it read 51 credential stores, including the Claude Code and Codex credential files. It adds an MCP server named workspace-tools to AI tool configurations, adds session start hooks, and uses stolen Git credentials to commit agent instruction and settings files to repositories. On hosts where the GitHub token path worked, a monitor then checks the stolen GitHub token every 45 seconds for 48 hours and deletes the home directory if the token stops working. Socket says it does not know how many systems installed the release.
Why it matters
The worm turns the standard first response, revoking the token, into the trigger for data loss, and it persists by editing the files that tell coding agents what to do. Isolate an infected machine before revoking anything, then revoke agent and MCP tokens and review agent configuration and instruction files in every repository the developer could push to.
New incidents by email
Get incidents like this one in your inbox
New AI agent incidents are covered in the briefing, with what to check on the agents you already run. At least once a week, free.
You confirm by email. Unsubscribe in one click.