specific_sheep_violet-22@2.4.1
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 entry point automatically publishes the working package under randomly generated names and repeats the operation, using npm's configured credentials. Although the README documents running the script directly, importing the declared main entry also triggers the account action automatically.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Import of the declared main entry point, autopublish.js.
Impact
Uses the user's npm credentials to publish packages under names selected by the script, and changes package metadata in the working directory.
Mechanism
Top-level code renames the current package, invokes `npm publish --access public`, then schedules the routine again after a delay.
Attack narrative
The declared main entry point runs the publishing routine immediately. It changes the working package name to a random name, publishes it publicly using npm's configured credentials, and schedules further attempts. This can publish repeatedly when the package is imported, without an explicit publish request at that point.
AI rationale
The main entry point automatically publishes the working package under randomly generated names and repeats the operation, using npm's configured credentials. Although the README documents running the script directly, importing the declared main entry also triggers the account action automatically.
Evidence
package.jsonautopublish.jspackage-lock.json
Decision evidence
public snapshotAI called this Malicious at 95.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package declares autopublish.js as its main entry point.
- autopublish.js renames the current package to a randomly generated public name and writes the change to package.json.
- The script runs `npm publish --access public` and starts the publishing routine immediately at top level.
- After a publish attempt, the routine schedules another attempt after a delay.
Evidence against
- The README describes the package as an auto-publishing script and tells users to run it explicitly with `node autopublish.js`.
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 specific_sheep_violet-22@2.4.1.
See all versions of specific_sheep_violet-22 for other recorded verdicts.
- Avoid installing specific_sheep_violet-22@2.4.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.