low_hummingbird_replicate_automation@2.2.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-aiautopublish3.js contains a concrete automated republishing routine that can expose a private project and repeatedly publish it using available npm credentials. It is not wired to an install hook in package.json, but its harmful behavior is explicit when the script is run.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Direct execution of autopublish3.js; the file calls checkAndRemovePrivate() at top level. No package install hook invokes it.
Impact
If run in a project with npm publishing credentials, it can publish that project publicly and repeatedly publish renamed versions using the user's npm account.
Mechanism
The script removes `private: true`, changes the version and package name, updates package-lock.json, runs `npm publish --access public`, then schedules another attempt.
Attack narrative
Directly running autopublish3.js starts a loop that changes package metadata, makes a private package public, and publishes it to npm under generated names. After a delay, it repeats. This can misuse available npm credentials to publish the user's project without an explicit publish request. The package manifest does not invoke the script through an install hook.
AI rationale
autopublish3.js contains a concrete automated republishing routine that can expose a private project and repeatedly publish it using available npm credentials. It is not wired to an install hook in package.json, but its harmful behavior is explicit when the script is run.
Evidence
autopublish3.jspackage.jsonpackage-lock.json
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- Running autopublish3.js automatically starts a routine that reads package.json and removes its private flag if set.
- The script changes the package version and name, and writes the changed metadata to package.json and package-lock.json.
- It runs `npm publish --access public` and schedules the routine to run again after a delay.
Evidence against
- package.json defines only dev, build, start, and lint scripts; it has no install lifecycle hook that invokes autopublish3.js.
- The inspected app entry page is a standard Next.js starter page and does not import the publishing script.
Behavioral surface
ChildProcessFilesystemShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
6 flaggedautopublish3.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.
autopublish3.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 = wet_rat_replicate_automation@2.3.1
matchedPath = autopublish2.js
matchedIdentity = npm:[redacted]:2.3.1
similarity = 1.000
shingleOverlap = 2
summary = package final verdict is malicious
Findings
1 Critical6 High5 Low
CriticalNpm Publish Wormautopublish3.js
HighChild Processautopublish3.js
HighShell
HighKnown Malware Source Fingerprint Signatureautopublish3.js
HighAi Review Evidenceautopublish3.js
HighAi Review Evidenceautopublish3.js
HighAi Review Evidenceautopublish3.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to low_hummingbird_replicate_automation@2.2.1.
See all versions of low_hummingbird_replicate_automation for other recorded verdicts.
- Avoid installing low_hummingbird_replicate_automation@2.2.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.