intimate_ostrich_amethyst-45@3.1.4
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 points to code that starts publishing immediately on import, changes the current project’s package metadata, and repeatedly runs public npm publishes. Although the README documents manual invocation, the package entry point makes importing it trigger unauthorized publishing with the user’s npm credentials.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Requiring the package’s main entry, or running autopublish.js directly.
Impact
Uses the user’s npm credentials to publish packages under generated names and repeatedly alters the project’s package metadata.
Mechanism
Changes package metadata, invokes `npm publish --access public`, then schedules another publish after a delay.
Attack narrative
The package’s main entry runs the publishing loop on import. It changes the current project’s package name, publishes it publicly using npm credentials, and schedules further publishes under generated names. This can publish a user’s package without a deliberate publish command and repeatedly mutate project metadata.
AI rationale
The `main` entry points to code that starts publishing immediately on import, changes the current project’s package metadata, and repeatedly runs public npm publishes. Although the README documents manual invocation, the package entry point makes importing it trigger unauthorized publishing with the user’s npm credentials.
Evidence
package.jsonautopublish.jspackage-lock.json
Network endpoints1
npmjs.com (via `npm publish`)
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Importing the package’s main entry starts the publishing loop immediately.
- The script changes the current project’s package name and writes package.json and package-lock.json.
- It runs `npm publish --access public` using the environment’s npm credentials.
- After publishing, it schedules another publish after a delay, repeating the cycle.
Evidence against
- The package description openly says it renames packages and publishes them to npm.
- The README documents manually running `node autopublish.js` as the intended use.
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 intimate_ostrich_amethyst-45@3.1.4.
See all versions of intimate_ostrich_amethyst-45 for other recorded verdicts.
- Avoid installing intimate_ostrich_amethyst-45@3.1.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.