hushed_zebra_green-81@2.4.2
Malicious code in hushed_zebra_green-81 (npm)
Analysis
hushed_zebra_green-81@2.4.2 ships a self-running package-publishing loop. Its entry point (main: autopublish.js, with autopublish2.js and autopublish3.js as variants) calls its publish routine unconditionally at module load, so the code executes as soon as the package is installed or required — no lifecycle hook and no user action required. When it runs it: reads the working directory's package.json; deletes the "private": true field so a private project becomes publishable; replaces the project name with a randomly generated fruit or adjective-animal string and randomizes the version; writes the same name into package-lock.json; then executes `npm publish --access public` through child_process.exec and schedules the same sequence again after a delay (30 seconds in autopublish2.js, 10 seconds in autopublish3.js, 1-5 minutes in autopublish.js), repeating indefinitely. The result is that the host project's own code is republished to the public npm registry under ever-changing random names using the npm credentials present on the machine, and the project's manifests are modified on disk each cycle. The package name itself follows the same adjective-animal-number pattern the code generates, so the published copies are the loop's own output. There is no hardcoded remote host, IP, or callback: publishing is performed locally by the npm CLI, so the package has no network IOC of its own beyond registry[.]npmjs[.]org.
- analyzed by
- Leitwacht
- first seen
- Nov 4, 2026, 09:05 AM
- analyzed
- Nov 4, 2026, 09:08 AM
Related advisories
- dependent-final@1.0.3
- inadequate_earwig_magenta-66@3.4.3
- @dreamguyxeon/libsignal-node@1.0.1
- ordered-btree@3.2.2
- @sauruslord/libsignal@2.0.2
- r-baileys@1.0.0
- malvin-baileys@2.2.1
- @alzx7z/baileys@2.0.6
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.