wet_rat_replicate_automation@2.3.1
This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
AI Security Review
scanned 3h ago · by lpm-firewall-aiautopublish2.js contains a concrete self-republishing loop that edits package metadata and invokes public npm publishing. It is not run by the declared lifecycle scripts, but the attack behavior is clear when the script is executed.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Running autopublish2.js directly; package.json does not invoke it automatically.
Impact
If run where npm publishing credentials are available, it can publish repeated package copies under generated names.
Mechanism
The script edits package metadata, generates a new package name and version, runs npm publish, then schedules another cycle.
Attack narrative
When executed, autopublish2.js changes package metadata, publishes the project to npm under a generated name, and schedules another publishing cycle. This behavior is unrelated to the included Next.js starter app. The manifest does not trigger the script during installation, so execution requires a separate direct invocation.
AI rationale
autopublish2.js contains a concrete self-republishing loop that edits package metadata and invokes public npm publishing. It is not run by the declared lifecycle scripts, but the attack behavior is clear when the script is executed.
Evidence
autopublish2.jspackage.jsonpackage-lock.json
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- When run, the script changes the package version to a random value.
- It renames the package with a generated name ending in `_replicate_automation` and writes the changed metadata to package.json.
- It runs `npm publish --access public`.
- After publishing, it schedules the process to repeat after a delay.
- The script starts its publishing routine at top level when executed.
Evidence against
- package.json has no install lifecycle scripts and does not expose autopublish2.js as a command.
- The app entry points are a standard Next.js starter page and layout.
Behavioral surface
ChildProcessFilesystemShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
6 flaggedautopublish2.jsView file
1const fs = require('fs');
L2: const { exec } = require('child_process');
L3: const { uniqueNamesGenerator, adjectives, colors, animals } = require('unique-names-generator');
...
L39:
L40: function checkAndRemovePrivate() {
L41: const animation = ['Sedang memeriksa package... ', 'Sedang memeriksa package. ', 'Sedang memeriksa package.. ', 'Sedang memeriksa package...'];
...
L43: const animationInterval = setInterval(() => {
L44: process.stdout.write('\r' + animation[currentFrame]);
L45: currentFrame = (currentFrame + 1) % animation.length;
...
L51: let packageJson = fs.readFileSync('package.json');
L52: let packageData = JSON.parse(packageJson);
L53: if (packageData.private === true) {
Critical
Npm Publish Worm
Source mutates package metadata and republishes itself to npm.
autopublish2.jsView on unpkg · L11const fs = require('fs');
L2: const { exec } = require('child_process');
L3: const { uniqueNamesGenerator, adjectives, colors, animals } = require('unique-names-generator');
High
•matchType = malicious_source_fingerprint_signature
signature = bd522058c93199a1
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = low_hummingbird_replicate_automation@2.2.1
matchedPath = autopublish3.js
matchedIdentity = npm:[redacted]:2.2.1
similarity = 1.000
shingleOverlap = 2
summary = package final verdict is malicious
Findings
1 Critical6 High5 Low
CriticalNpm Publish Wormautopublish2.js
HighChild Processautopublish2.js
HighShell
HighKnown Malware Source Fingerprint Signatureautopublish2.js
HighAi Review Evidenceautopublish2.js
HighAi Review Evidenceautopublish2.js
HighAi Review Evidenceautopublish2.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to wet_rat_replicate_automation@2.3.1.
See all versions of wet_rat_replicate_automation for other recorded verdicts.
- Avoid installing wet_rat_replicate_automation@2.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.