Worm armed 42 GitHub repos by hiding a payload too big to fail
Miasma-family npm worm hid large payloads to evade GitHub scans, compromising 42 repositories.
A new Miasma-family npm worm, initially thought to be a test, secretly compromised 42 GitHub repositories from 11 owners. The worm used large payload blobs (12.9-13.7 MB) to evade GitHub's code search and automated scanners. It also steals credentials, modifies repositories, and installs a wiper that deletes the home directory upon token revocation.
AI summary of the linked source. Not reviewed by an editor. How this works
Run npm?
Get an email when a new story names npm, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonA worm from the Miasma npm family compromised 42 GitHub repositories by embedding payloads between 12.9–13.7 MB — deliberately sized to exceed the indexing thresholds of GitHub's code search and automated security scanners, rendering them effectively invisible to standard tooling. Beyond persistence, the worm stole credentials, silently modified repository contents, and deployed a destructive wiper that erased the victim's home directory if their access token was revoked. This incident exposes a critical blind spot: security tooling that relies on size-based heuristics or index limits can be systematically exploited. It also illustrates how a single compromised package in the npm ecosystem can cascade laterally across multiple repositories and owners. Organizations trusting open-source registries without independent verification of package integrity are directly in this attack's blast radius.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Threat intelligence
Attack campaigns reach your sector, suppliers or software before your team hears about them.
- Software supply chain security
Malicious and vulnerable open-source packages are caught before they ship.
Indicators of Compromise
Extracted by AI from the linked source. Not reviewed by an editor. How this works
- cve — CVE-2026-41940