valid_antlion_amber-50@4.1.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 13h ago · by lpm-firewall-aiThe main module starts a loop that renames the current package and publishes it publicly with the user's npm credentials. Although the README describes running the script directly, importing the package also triggers publishing without a distinct request.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Module import or execution of `autopublish.js`; the publishing function is called at top level.
Impact
An import can publish packages using the user's npm credentials and repeatedly change the project's package name and lockfile without a distinct publish request.
Mechanism
The script rewrites package metadata, invokes `npm publish --access public`, then schedules another publish after a random delay.
Attack narrative
The package's main entry points to `autopublish.js`, which immediately changes the current package name, publishes it publicly, and schedules another publish. Importing it can therefore use the user's npm credentials to publish randomized package names and modify project metadata without a separate publish request. The README documents running the script directly, but the main entry also makes the behavior reachable through import.
AI rationale
The main module starts a loop that renames the current package and publishes it publicly with the user's npm credentials. Although the README describes running the script directly, importing the package also triggers publishing without a distinct request.
Evidence
package.jsonautopublish.jspackage-lock.json
Network endpoints1
npmjs.com
Decision evidence
public snapshotAI called this Malicious at 95.0% confidence as Malware with low false-positive risk.
Evidence for block
- `package.json` sets `autopublish.js` as the main module, so requiring the package loads the publishing script.
- The script changes the current package name to a random value and writes the change to `package.json` and `package-lock.json`.
- It runs `npm publish --access public` and schedules further publishing after a delay.
- The script calls `publishWithDelay()` at top level, without requiring a separate command or confirmation.
Evidence against
- The README describes a tool for renaming and publishing packages and tells users to run `node autopublish.js` explicitly.
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 valid_antlion_amber-50@4.1.3.
See all versions of valid_antlion_amber-50 for other recorded verdicts.
- Avoid installing valid_antlion_amber-50@4.1.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.