hushed_zebra_green-81@2.4.2
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
AI Security Review
scanned 13h ago · by lpm-firewall-aiThe main entry starts an unbounded publishing loop on import and repeatedly publishes under generated names using the caller's npm credentials. The README describes manual execution, but the manifest makes this behavior automatic for consumers who load the package.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Module load through the package's main entry, autopublish.js.
Impact
Publishes packages under the invoking user's npm credentials without a separate request for each publication, potentially flooding the registry and affecting the user's npm account.
Mechanism
The script rewrites package.json and package-lock.json, invokes npm publish --access public, then schedules itself to publish again after a delay.
Attack narrative
The package's main entry starts a publishing loop as soon as it is loaded. It assigns the package a random name, updates the lockfile, publishes publicly through npm, and schedules another attempt. This can use the invoking user's npm credentials to make repeated publications without separate confirmation for each one.
AI rationale
The main entry starts an unbounded publishing loop on import and repeatedly publishes under generated names using the caller's npm credentials. The README describes manual execution, but the manifest makes this behavior automatic for consumers who load the package.
Evidence
package.jsonautopublish.jsREADME.mdpackage-lock.json
Network endpoints1
npmjs.com
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package manifest sets autopublish.js as the main entry point.
- Loading the main file starts publishing at top level, without an explicit function call from the importer.
- The script changes package.json to a randomly generated name, updates package-lock.json, and runs npm publish --access public.
- After each publish attempt, it schedules another publish; the entry point starts this loop immediately.
Evidence against
- The README describes the script as an automatic npm publishing tool and tells users to run it with node autopublish.js.
- The manifest declares no install or postinstall lifecycle hook.
Behavioral surface
ChildProcessFilesystemShell
HighEntropyStrings
Source & flagged code
7 flaggedautopublish.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 · L11Trigger-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 · L1Findings
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
HighAi Review Evidenceautopublish.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to hushed_zebra_green-81@2.4.2.
See all versions of hushed_zebra_green-81 for other recorded verdicts.
- Avoid installing hushed_zebra_green-81@2.4.2. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.