registry / Malware / unfortunate_crawdad_emerald-79

unfortunate_crawdad_emerald-79

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 unfortunate_crawdad_emerald-79@3.3.1, the only known version.

AI Security Review

scanned 10h ago · by lpm-firewall-ai

The main entrypoint automatically mutates the caller's package metadata and repeatedly publishes the project using the user's npm account. The README documents the script's purpose, but import-triggered publishing can expose and republish a consuming project's contents without a distinct publish request.

Static reason

High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review

Trigger

Import or execution of autopublish.js; its top-level call starts the routine immediately.

Impact

Can publish project contents publicly under generated names and repeatedly use the user's npm publishing account.

Mechanism

Rewrites package.json and package-lock.json with a generated package name, runs `npm publish --access public`, then schedules another publish after a delay.

Attack narrative

The package's main entrypoint starts publishing immediately. It renames the package metadata in the current working directory, publishes it publicly with the available npm credentials, and repeats the process after a delay. Importing it into another project can therefore publish that project's contents under generated names without a separate publish request.

AI rationale

Evidence

package.jsonautopublish.jspackage-lock.json

Network endpoints1

npmjs.com

Decision evidence

public snapshot

AI called this Malicious at 97.0% confidence as Malware with low false-positive risk.

Evidence for block

The manifest sets autopublish.js as the package main entrypoint.
On execution, autopublish.js changes the current project's package name and writes the modified package.json.
It also changes package-lock.json and runs `npm publish --access public`.
The file invokes the publish routine at top level and schedules it to repeat after each attempt.

Evidence against

The README describes the package as an automatic npm publishing script and instructs users to run it directly.
No install lifecycle scripts are declared 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 unfortunate_crawdad_emerald-79@3.3.1.

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

Avoid installing unfortunate_crawdad_emerald-79@3.3.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: 2026-11-04 10:01:10.797Z (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

3.3.1latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 8:33 PM

registry / Malware / unfortunate_crawdad_emerald-79

unfortunate_crawdad_emerald-79

This report shows the evidence for unfortunate_crawdad_emerald-79@3.3.1, the only known version.

AI Security Review

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

Import or execution of autopublish.js; its top-level call starts the routine immediately.

Impact

Can publish project contents publicly under generated names and repeatedly use the user's npm publishing account.

Mechanism

Rewrites package.json and package-lock.json with a generated package name, runs `npm publish --access public`, then schedules another publish after a delay.

Attack narrative

AI rationale

Evidence

package.jsonautopublish.jspackage-lock.json

Network endpoints1

npmjs.com

Decision evidence

public snapshot

AI called this Malicious at 97.0% confidence as Malware with low false-positive risk.

Evidence for block

The manifest sets autopublish.js as the package main entrypoint.
On execution, autopublish.js changes the current project's package name and writes the modified package.json.
It also changes package-lock.json and runs `npm publish --access public`.
The file invokes the publish routine at top level and schedules it to repeat after each attempt.

Evidence against

The README describes the package as an automatic npm publishing script and instructs users to run it directly.
No install lifecycle scripts are declared 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 unfortunate_crawdad_emerald-79@3.3.1.

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

Avoid installing unfortunate_crawdad_emerald-79@3.3.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: 2026-11-04 10:01:10.797Z (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

3.3.1latestshownMaliciousMalwareBlockPublishedMay 21, 2024, 8:33 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