low_hummingbird_replicate_automation@2.2.1
Malicious code in low_hummingbird_replicate_automation (npm)
Analysis
This package is a Next.js boilerplate republished by an automated, self-replicating publish worm rather than a usable library. It ships package/autopublish3.js, which requires fs and child_process and, when run, reads ./package.json and if `private` is true deletes that field and rewrites the file; generates a random version of the form `1-4.1-4.1-4` and writes it to package.json; renames the package to a randomly generated `<word>_replicate_automation` name (built from unique-names-generator adjective/animal/colour dictionaries) and rewrites name in package-lock.json to match; then invokes `npm publish --access public` through child_process.exec and repeats the whole cycle every 60 seconds with a new random identity, endlessly cloning itself under fresh npm package names (the package's own name follows the same generator). The package declares no preinstall/postinstall or other lifecycle hook and no bin entry, so installing it does not execute the script. The script contains no network code, no C2 endpoint, no host fingerprinting and no credential or environment access — it does not read, collect or transmit npm credentials, .npmrc contents, environment variables or files; it only drives the local npm CLI, which uses its own configured credentials. There is no remote network IOC in the package; the observable artefact is the mass-created `<random-word>_replicate_automation` name family appearing on the public registry.
- analyzed by
- Leitwacht
- first seen
- Nov 5, 2026, 05:05 AM
- analyzed
- Nov 5, 2026, 05:06 AM
Related advisories
- inadequate_earwig_magenta-66@3.4.3
- @ubedsockets/baileys@1.6.7
- @ubedsockets/baileys@1.6.3
- @axo_cuy/baileyss@1.0.0
- character-ai-sdk@1.0.1
- litecore-lib-ltc@1.9.3
- raiden-baileys@2.1.6
- @ubedsockets/baileys@1.7.12
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.