inadequate_earwig_magenta-66@3.4.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 10h ago · by lpm-firewall-aiThe package's main entrypoint automatically alters package metadata and publishes publicly, then repeats the action on a timer. Although the README documents running the script directly, the same behavior is reachable simply by importing the package.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Importing the package through its main entrypoint, or running autopublish.js directly.
Impact
Can publish the user's project under randomly generated package names and continue publishing without a separate confirmation for each run.
Mechanism
Top-level code changes package metadata, invokes npm publish --access public, and schedules further publishing.
Attack narrative
The main entrypoint immediately renames the current project, publishes it publicly with npm, and schedules another publish; importing this package can therefore trigger repeated publishing under the user's npm credentials.
AI rationale
The package's main entrypoint automatically alters package metadata and publishes publicly, then repeats the action on a timer. Although the README documents running the script directly, the same behavior is reachable simply by importing the package.
Evidence
package.jsonautopublish.jsREADME.mdpackage-lock.json
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package declares autopublish.js as its main entrypoint.
- At module load, autopublish.js immediately starts its publishing routine.
- The routine changes the current package name to a randomly generated name and writes package.json and package-lock.json.
- It runs npm publish --access public, then schedules another publish after a delay.
Evidence against
- The README describes the project as an auto-publishing script and documents running it explicitly with node autopublish.js.
- The manifest declares no install or postinstall lifecycle script.
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 inadequate_earwig_magenta-66@3.4.3.
See all versions of inadequate_earwig_magenta-66 for other recorded verdicts.
- Avoid installing inadequate_earwig_magenta-66@3.4.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.