Which versions of motionless_mandrill_blush-51 are malicious?

The following npm versions of motionless_mandrill_blush-51 are flagged malicious: 2.2.3. Treat any of these as compromised.

How do I remediate motionless_mandrill_blush-51 if I installed it?

motionless_mandrill_blush-51 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed motionless_mandrill_blush-51 — how do I know if it already compromised me?

If motionless_mandrill_blush-51 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find motionless_mandrill_blush-51 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for motionless_mandrill_blush-51 (version 2.2.3).

Malicious package

motionless_mandrill_blush-51npm

Advisory published Nov 2, 2026Updated Nov 4, 2026

motionless_mandrill_blush-51 is a confirmed malicious npm package (MAL-2026-18614) that opens a backdoor for remote access (malicious version 2.2.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in motionless_mandrill_blush-51 (npm)

MAL-2026-18614

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall motionless_mandrill_blush-51

What this malware does

Part of a self-republishing campaign: generated names of the form <adjective><animal><colour>-<number>, each package shipping the same autopublish.js, which runs npm publish --access public to publish the package again. Self-replicating publication is the propagation step of a registry worm and fills the registry with copies. Version examined: 2.2.3; tarball SHA-256 b524996b7179cbc2702ad62f3d2917241f9cf8ad5d559202eac825ebd7cd9844.

Malicious versions

1 flagged

2.2.3

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for motionless_mandrill_blush-51 (version 2.2.3).
If you installed it — respond
motionless_mandrill_blush-51 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If motionless_mandrill_blush-51 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. motionless_mandrill_blush-51 on npm has been identified as a malicious package (version 2.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Oluwatosin Amokeodo · finder

Detect & block this

O3 blocks motionless_mandrill_blush-51-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database