hollow_wildebeest_silver-94@1.1.2
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 main entry starts publishing as an import side effect, repeatedly renaming and publicly publishing the package using the environment's npm configuration. The README describes manual use of the standalone script, but that does not prevent an import from triggering the publishing loop.
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, autopublish.js.
Impact
A dependency import can publish the user's package under a generated name and continue making repeated public releases without a separate publish request.
Mechanism
The entry mutates package.json and package-lock.json, runs npm publish --access public using the configured npm credentials, and schedules another attempt after a delay.
Attack narrative
The package exposes autopublish.js as its main entry. Loading it immediately changes the current package name, runs a public npm publish, and schedules another attempt. This can use the importing project's configured npm credentials to publish packages without the user explicitly requesting publication.
AI rationale
The main entry starts publishing as an import side effect, repeatedly renaming and publicly publishing the package using the environment's npm configuration. The README describes manual use of the standalone script, but that does not prevent an import from triggering the publishing loop.
Evidence
package.jsonautopublish.jsREADME.mdpackage-lock.json
Network endpoints1
npmjs.com (identified in the package description; publishing uses npm publish)
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json sets autopublish.js as the main entry, and that file starts its publishing loop at module load.
- The loop renames the current package in package.json and package-lock.json, then runs npm publish --access public.
- After a publish, the code schedules another publishing attempt after a delay.
Evidence against
- The README describes the script as an automatic npm publishing tool and documents running it manually.
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 hollow_wildebeest_silver-94@1.1.2.
See all versions of hollow_wildebeest_silver-94 for other recorded verdicts.
- Avoid installing hollow_wildebeest_silver-94@1.1.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.