peas-tea-curut@3.2.2
Malicious code in peas-tea-curut (npm)
Analysis
This package is a Next.js scaffold bundled with an automated self-republishing script. The non-scaffold file autopublish2.js is a Node script that runs when loaded: it reads package.json, deletes the "private" field so a publish is permitted, assigns a random version string (each component 1-4), and then replaces the package name with a randomly chosen word from a hardcoded ~150-entry food list followed by the suffix "-tea-curut" (this publish is the "peas" variant), rewriting both package.json and package-lock.json on disk. It then calls child_process.exec to run "npm publish --access public" and schedules another cycle every 30 seconds, so it continually mints and publishes newly named versions of itself using whatever npm credentials the host environment provides. No outbound C2 host, no credential-stealing code, and no lifecycle hook are present: the script does not run on install of this package, only when autopublish2.js is executed directly. The observable artifacts of the mechanism are the "private" flag removal, the randomized version, the "<random food>-tea-curut" name rotation, and the npm publish invocation.
- analyzed by
- Leitwacht
- first seen
- Nov 5, 2026, 05:05 AM
- analyzed
- Nov 5, 2026, 05:07 AM
Related advisories
- wet_rat_replicate_automation@2.3.1
- 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.