itchy_gecko_magenta-98@2.3.4
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 package’s import entry automatically rewrites package metadata and repeatedly publishes to npm using available credentials. Although the README describes a user-run publishing script, the `main` entry makes these account actions reachable merely 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 entry point; no install lifecycle hook is declared.
Impact
Uses available npm credentials to repeatedly publish under generated package names and alters the working package metadata.
Mechanism
Top-level code renames the package, writes package metadata, runs `npm publish --access public`, then schedules another publish.
Attack narrative
The main entry points to autopublish.js, and that file starts publishing at module load. It changes the current package name, writes package.json and package-lock.json, invokes `npm publish --access public`, and schedules another attempt after a delay. This can use the environment’s npm credentials to publish repeatedly under generated names without an explicit publishing command by the importing application.
AI rationale
The package’s import entry automatically rewrites package metadata and repeatedly publishes to npm using available credentials. Although the README describes a user-run publishing script, the `main` entry makes these account actions reachable merely by importing the package.
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 points to autopublish.js, which starts its publishing routine at module load.
- The routine renames the current package and writes the changed name to package.json and package-lock.json.
- It runs `npm publish --access public` and schedules repeated publishing after a delay.
Evidence against
- The README documents publishing as the script’s purpose and tells users to run it with `node autopublish.js`.
- The manifest declares no install lifecycle scripts.
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 itchy_gecko_magenta-98@2.3.4.
See all versions of itchy_gecko_magenta-98 for other recorded verdicts.
- Avoid installing itchy_gecko_magenta-98@2.3.4. 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.