smooth_angelfish_emerald-54@2.2.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 12h ago · by lpm-firewall-aiThe main entrypoint triggers repeated public package publishing and rewrites project metadata without an importer's explicit request to publish. The README advertises the script's behavior, but that does not make publishing on package import an authorized action.
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 repeated, arbitrarily renamed packages using the user's npm credentials and alter package metadata in the working directory.
Mechanism
The script rewrites package metadata with a random name, publishes it publicly with npm, then schedules another publish after a random delay.
Attack narrative
The package's main entrypoint immediately starts autopublish.js. The script renames the package in the current directory, updates package-lock.json, publishes it publicly, and repeats on a timer. Although the README describes direct use of the publishing script, consumers importing the package also trigger publishing as a side effect.
AI rationale
The main entrypoint triggers repeated public package publishing and rewrites project metadata without an importer's explicit request to publish. The README advertises the script's behavior, but that does not make publishing on package import an authorized action.
Evidence
package.jsonautopublish.jspackage-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 main is autopublish.js, so importing the package runs that file.
- The script changes the current package name to a randomly generated name and writes it to package.json and package-lock.json.
- It runs `npm publish --access public` and schedules the same publishing function again after a delay.
Evidence against
- The README describes the package as an auto-publishing script and tells users to run it directly.
- There is no install lifecycle script in package.json.
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 smooth_angelfish_emerald-54@2.2.2.
See all versions of smooth_angelfish_emerald-54 for other recorded verdicts.
- Avoid installing smooth_angelfish_emerald-54@2.2.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.