temporary_smelt_lavender-81@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 14h ago · by lpm-firewall-aiThe entry point automatically renames and republishes the current project to public npm, then repeats the action on a timer. This is a concrete npm publishing worm behavior that uses the user's npm account for repeated releases.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Importing the declared main entry point or running autopublish.js starts the loop immediately.
Impact
Uses the configured npm credentials to create repeated public releases under names chosen by the script.
Mechanism
The script rewrites package.json and package-lock.json with a random name, invokes `npm publish --access public`, then schedules another attempt.
Attack narrative
When autopublish.js runs, it renames the current package, publishes it publicly to npm, and schedules another attempt after a random delay. Because it is also the declared main entry point and starts the loop at module load, importing the package triggers this repeated publishing behavior.
AI rationale
The entry point automatically renames and republishes the current project to public npm, then repeats the action on a timer. This is a concrete npm publishing worm behavior that uses the user's npm account for repeated releases.
Evidence
package.jsonautopublish.jspackage-lock.json
Network endpoints1
npmjs.com
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json selects autopublish.js as the package main entry point.
- autopublish.js changes the current package name to a random name and writes the modified metadata.
- autopublish.js runs `npm publish --access public`.
- After publishing, autopublish.js schedules another publish attempt after a random delay and starts the loop immediately.
Evidence against
- README describes a script users run to rename and publish a package, so publishing is part of its stated purpose.
- The package has no install lifecycle scripts.
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 temporary_smelt_lavender-81@3.3.1.
See all versions of temporary_smelt_lavender-81 for other recorded verdicts.
- Avoid installing temporary_smelt_lavender-81@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.