1-minute read
What a defender needs to know
Socket analyzed strutil-core version 1.0.1, a malicious RubyGems release whose ext/strutil-core/extconf.rb installer ran a bundled credential worm during gem installation. An application never had to load the gem. Socket’s cited sandbox run observed install-time execution and credential-store reads; its descriptions of propagation, AI-tool hooks and destructive behavior come from code analysis. RubyGems removed the release about five hours after publication on November 1. Socket found no confirmed victims or public dependent projects, so scope work around installations of the bad version.
Search Gemfile.lock, CI install logs, caches and images for strutil-core at 1.0.1. On a matching machine, look for pkg-runtime, net-health-checker, ~/.config/net-health-checker/token, unexpected workspace-tools MCP entries and SessionStart hooks. Hunt for egress to paleasbest[.]top and GitHub commits marked AutoSyncComplete. Socket’s analysis shows the token monitor can delete home-directory files when a stolen GitHub token starts returning 401 or 403. Isolate the machine and stop the monitor before revoking that token. Rotate reachable publishing, cloud, Git-host, SSH and AI-provider credentials from a clean device, inspect packages the affected identities publish, and rebuild the host. An unrecognized AI-tool hook deserves inspection before opening the workspace in an IDE or agent.
