colossal_wallaby_pink-87
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 colossal_wallaby_pink-87@1.2.1, the only known version.
AI Security Review
scanned 10h ago · by lpm-firewall-aiThe main entry automatically mutates the importing project's package metadata and repeatedly publishes it publicly to npm under generated names. This uses the caller's npm credentials for an unrequested publishing action, so the package is malicious.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Module import; `autopublish.js` invokes the publishing function at top level.
Impact
The user's project may be published publicly under generated names using their npm credentials, with repeated publications and changes to local package files.
Mechanism
The script rewrites package metadata with a generated name, executes `npm publish --access public`, then schedules another attempt after a random delay.
Attack narrative
On import, the main entry changes the current project's name in package metadata and runs `npm publish --access public`. It then schedules repeated publishing attempts, using the caller's npm authentication to publish project contents under generated names.
AI rationale
The main entry automatically mutates the importing project's package metadata and repeatedly publishes it publicly to npm under generated names. This uses the caller's npm credentials for an unrequested publishing action, so the package is malicious.
Evidence
package.jsonautopublish.jspackage-lock.json
Network endpoints1
npmjs.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package main entry is `autopublish.js`, and the package description says it renames package metadata and publishes to npm.
- The script changes the current project's package name and writes the change to `package.json` and `package-lock.json`.
- It runs `npm publish --access public`, using the environment's npm authentication to publish the renamed project.
- The publish loop starts at module load and schedules another publish after each attempt.
Evidence against
- The README describes the tool as an auto-publishing script and tells users to run `autopublish.js` 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 colossal_wallaby_pink-87@1.2.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing colossal_wallaby_pink-87@1.2.1. 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.