registry / Malware / smooth_angelfish_emerald-54

smooth_angelfish_emerald-54

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 smooth_angelfish_emerald-54@2.2.2, the only known version.

AI Security Review

scanned 11h ago · by lpm-firewall-ai

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.

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

Evidence

package.jsonautopublish.jspackage-lock.json

Network endpoints1

npmjs.com

Decision evidence

public snapshot

AI 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

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 smooth_angelfish_emerald-54@2.2.2.

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

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: 2026-11-04 09:51:45.082Z (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.2.2latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 8:44 PM

registry / Malware / smooth_angelfish_emerald-54

smooth_angelfish_emerald-54

This report shows the evidence for smooth_angelfish_emerald-54@2.2.2, the only known version.

AI Security Review

scanned 11h 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 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

AI rationale

Evidence

package.jsonautopublish.jspackage-lock.json

Network endpoints1

npmjs.com

Decision evidence

public snapshot

AI 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

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 smooth_angelfish_emerald-54@2.2.2.

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

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: 2026-11-04 09:51:45.082Z (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.2.2latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 8:44 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