unfortunate_crawdad_emerald-79@3.3.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 11h ago · by lpm-firewall-aiThe 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
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.
Evidence
package.jsonautopublish.jspackage-lock.json
Network endpoints1
npmjs.com
Decision evidence
public snapshotAI 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
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 unfortunate_crawdad_emerald-79@3.3.1.
See all versions of unfortunate_crawdad_emerald-79 for other recorded verdicts.
- 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.