1-minute read
What a defender needs to know
CrowdStrike says Glassworm stole developer credentials and used them to force-push malicious code into the default branches of more than 300 GitHub repositories. Earlier infections arrived through trojanized OpenVSX extensions and compromised npm and Python packages.
The malware ran on Windows, macOS and Linux. Its command infrastructure used Solana transaction memos, BitTorrent DHT records, Google Calendar event titles and commercial virtual servers. CrowdStrike, Google and the Shadowserver Foundation disrupted all four channels on May 26.
CrowdStrike now operates the IP address 164.92.88[.]210, which infected systems beacon to after the takedown. A connection indicates a Glassworm infection, but the host may have lost credentials before command traffic was cut.
Revoke the affected developer’s active sessions, GitHub and registry tokens, OAuth grants and SSH keys. Audit force-push events, default-branch history, workflow changes, package publications and release artifacts for the exposure window. If altered source reached a shared branch or registry, inspect downstream builds as well.
Managed developer endpoints should retain an inventory of installed IDE extensions and package-install events. Cleaning the workstation addresses the malware on that host. The repository and publishing review determines whether the stolen authority changed software other people received.
Verify that the endpoint is clean, revoke exposed publishing credentials, and compare released artifacts with their expected source and provenance.