wet_rat_replicate_automation@2.3.1
Malicious code in wet_rat_replicate_automation (npm)
Analysis
This package is a create-next-app scaffold bundled with a self-replicating mass-publish script, package/autopublish2.js. The package declares no lifecycle hook or bin, so the script is not run on install; when executed it drives an unattended publish loop against the npm registry. Each iteration reads package.json and, if "private": true is set, deletes that field and rewrites the file, replaces the version with a random 1-4.1-4.1-4 value, and renames the package to a generated <adjective>_<animal|color>_replicate_automation string, writing the same name into package-lock.json. It then spawns `npm publish --access public` through child_process.exec and repeats itself after a fixed 30-second delay, indefinitely, with a branch specifically for handling "429 Too Many Requests". The randomization of name and version per iteration is what keeps the flood going past registry throttling and defeats takedown by package name; this release's own name, wet_rat_replicate_automation, matches the generated template. The republished copies inherit the dependencies arts-dao ^1.1.4, gula-dao ^1.1.4 and ksni-technical-test ^1.1.8. The package contains no credential, token or file access and no network destination other than the npm registry — the abuse is registry flooding, not local compromise. No C2 host or IP is present in the code.
- analyzed by
- Leitwacht
- first seen
- Nov 5, 2026, 05:05 AM
- analyzed
- Nov 5, 2026, 05:07 AM
Related advisories
- your-unique-package-name1@1.0.0
- hushed_zebra_green-81@2.4.2
- 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
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.