LWA-2026-13652 confirmed malware

motionless_mandrill_blush-51@2.2.3

Malicious code in motionless_mandrill_blush-51 (npm)

Analysis

This package ships registry publish-abuse tooling rather than a usable library. Its three scripts (autopublish.js, autopublish2.js, autopublish3.js) read the current project's package.json and package-lock.json, overwrite the package name with a randomized identity (fruit/vegetable words, or unique-names-generator adjectives/animals/colors output), overwrite the version with a random 1-4.1-4.1-4 value, and delete any "private": true field so the project becomes publishable. The script then runs child_process.exec("npm publish --access public") and loops the rename-and-publish cycle indefinitely, sleeping a randomized 10s-5min between publishes and stopping only on a 429 rate-limit response from registry[.]npmjs[.]org. Its effect is to mass-publish randomly named, randomly versioned packages to the npm registry under the operator's own credentials, using identity randomization to make the flood hard to correlate. Installing the package executes nothing: package.json declares no preinstall/postinstall step and no bin entry. No credential, token or environment read, no network client and no obfuscated payload are present in the shipped files.

analyzed by
Leitwacht
first seen
Nov 4, 2026, 09:05 AM
analyzed
Nov 4, 2026, 09:08 AM

Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.