registry / Malware / motionless_mandrill_blush-51

motionless_mandrill_blush-51

Ini adalah script Node.js yang bisa auto ganti nama package dalam file `package.json` dan `package-lock.json`, serta bisa publish package ke npmjs.com dengan`npm publish`. Script ini memiliki jeda waktu 1-5 menit untuk publish package selanjutnya. Sambil

This report shows the evidence for motionless_mandrill_blush-51@2.2.3, the only known version.

AI Security Review

scanned 10h ago · by lpm-firewall-ai

The package’s main entrypoint starts an unbounded publishing loop that rewrites the current project metadata and publishes publicly using npm’s credentials. Although the README describes the script, importing the package triggers this account action automatically.

Static reason

High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review

Trigger

Importing the package or running autopublish.js starts the publishing loop.

Impact

A consumer can have their project published publicly under generated names without intending to publish it; the loop can continue publishing until stopped.

Mechanism

The script rewrites package metadata, invokes npm publish with public access, and schedules repeated runs using the local npm credentials.

Attack narrative

Loading the package starts autopublish.js. It changes the current project’s package name, publishes it publicly using npm’s configured credentials, and schedules another publish after a delay. This can expose a consumer’s project and repeatedly publish under generated names without an explicit publish request.

AI rationale

Evidence

package.jsonautopublish.jsREADME.mdpackage-lock.json

Network endpoints1

npmjs.com

Decision evidence

public snapshot

AI called this Malicious at 97.0% confidence as Malware with low false-positive risk.

Evidence for block

The package main is autopublish.js, which calls publishWithDelay() at module load.
autopublish.js changes the current package name and writes package.json and package-lock.json.
It runs npm publish --access public, then schedules another publish after a delay.
The README identifies npmjs.com as the publishing destination and describes repeated publishing.

Evidence against

The README openly describes the auto-renaming and publishing behavior and tells users to run the script.
package.json declares no install lifecycle scripts.

Behavioral surface

Source

ChildProcessFilesystemShell

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 14.2 KB of source

Source & flagged code

7 flagged

autopublish.jsView file

1const fs = require('fs'); L2: const { exec } = require('child_process'); L3: ... L28: const animationInterval = setInterval(() => { L29: process.stdout.write('\r' + animation[currentFrame]); L30: currentFrame = (currentFrame + 1) % animation.length; ... L32: L33: let packageJson = fs.readFileSync('package.json'); L34: let packageData = JSON.parse(packageJson); L35: let randomString = generateRandomString(10); ... L45: L46: exec('npm publish --access public', (error, stdout, stderr) => {

Critical

Npm Publish Worm

Source mutates package metadata and republishes itself to npm.

autopublish.jsView on unpkg · L1

1Trigger-reachable chain: manifest.main -> autopublish.js L1: const fs = require('fs'); L2: const { exec } = require('child_process'); L3: ... L28: const animationInterval = setInterval(() => { L29: process.stdout.write('\r' + animation[currentFrame]); L30: currentFrame = (currentFrame + 1) % animation.length; ... L32: L33: let packageJson = fs.readFileSync('package.json'); L34: let packageData = JSON.parse(packageJson); L35: let randomString = generateRandomString(10); ... L45: L46: exec('npm publish --access public', (error, stdout, stderr) => {

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

autopublish.jsView on unpkg · L1

Findings

2 Critical6 High1 Medium3 Low

CriticalNpm Publish Wormautopublish.js

CriticalTrigger Reachable Dangerous Capabilityautopublish.js

HighChild Processautopublish.js

HighShell

HighKnown Malware Source Fingerprint Signatureautopublish3.js

HighAi Review Evidencepackage.json

HighAi Review Evidenceautopublish.js

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

Affected versions and remediation

This report applies to motionless_mandrill_blush-51@2.2.3.

The versions list below shows the verdict for each recorded version.

Avoid installing motionless_mandrill_blush-51@2.2.3. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-11-04 09:50:51.253Z (UTC).

Source advisory published: 2026-11-02 09:44:21.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

1 known version

2.2.3latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 7:10 PM

registry / Malware / motionless_mandrill_blush-51

motionless_mandrill_blush-51

This report shows the evidence for motionless_mandrill_blush-51@2.2.3, the only known version.

AI Security Review

scanned 10h ago · by lpm-firewall-ai

Static reason

High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review

Trigger

Importing the package or running autopublish.js starts the publishing loop.

Impact

A consumer can have their project published publicly under generated names without intending to publish it; the loop can continue publishing until stopped.

Mechanism

The script rewrites package metadata, invokes npm publish with public access, and schedules repeated runs using the local npm credentials.

Attack narrative

AI rationale

Evidence

package.jsonautopublish.jsREADME.mdpackage-lock.json

Network endpoints1

npmjs.com

Decision evidence

public snapshot

AI called this Malicious at 97.0% confidence as Malware with low false-positive risk.

Evidence for block

The package main is autopublish.js, which calls publishWithDelay() at module load.
autopublish.js changes the current package name and writes package.json and package-lock.json.
It runs npm publish --access public, then schedules another publish after a delay.
The README identifies npmjs.com as the publishing destination and describes repeated publishing.

Evidence against

The README openly describes the auto-renaming and publishing behavior and tells users to run the script.
package.json declares no install lifecycle scripts.

Behavioral surface

Source

ChildProcessFilesystemShell

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 14.2 KB of source

Source & flagged code

7 flagged

autopublish.jsView file

Critical

Npm Publish Worm

Source mutates package metadata and republishes itself to npm.

autopublish.jsView on unpkg · L1

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

autopublish.jsView on unpkg · L1

Findings

2 Critical6 High1 Medium3 Low

CriticalNpm Publish Wormautopublish.js

CriticalTrigger Reachable Dangerous Capabilityautopublish.js

HighChild Processautopublish.js

HighShell

HighKnown Malware Source Fingerprint Signatureautopublish3.js

HighAi Review Evidencepackage.json

HighAi Review Evidenceautopublish.js

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

Affected versions and remediation

This report applies to motionless_mandrill_blush-51@2.2.3.

The versions list below shows the verdict for each recorded version.

Avoid installing motionless_mandrill_blush-51@2.2.3. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-11-04 09:50:51.253Z (UTC).

Source advisory published: 2026-11-02 09:44:21.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

1 known version

2.2.3latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 7:10 PM

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

Versions

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other malware packages

Related packages

Other malware packages