quiche-tea-curut@4.3.4
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 self-repeating routine that alters package metadata and publishes publicly through npm. It is not wired to install or app startup, but the bundled script's publishing behavior is concrete and unrelated to the package's Next.js app.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Executing autopublish2.js directly; it is not invoked by the declared package scripts or imports.
Impact
Uses the invoking user's npm publishing credentials to publish packages without a clear user request, potentially exposing project contents and repeating publication.
Mechanism
It edits package.json and package-lock.json, removes the private flag if present, changes the version and name, runs npm publish --access public, then schedules another cycle.
Attack narrative
When run directly, autopublish2.js changes the current package's metadata, removes its private flag, and publishes it publicly under a randomized fruit-based name. It then schedules the process to repeat, using the caller's npm configuration and credentials. The manifest does not trigger the script automatically, but the bundled file contains a concrete republishing worm routine.
AI rationale
autopublish2.js contains a self-repeating routine that alters package metadata and publishes publicly through npm. It is not wired to install or app startup, but the bundled script's publishing behavior is concrete and unrelated to the package's Next.js app.
Evidence
autopublish2.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
- autopublish2.js removes the private flag and rewrites package.json so the package can be published publicly.
- The script assigns a randomized version and changes the package name to a randomly selected fruit name followed by -tea-curut.
- It runs npm publish --access public and schedules checkAndRemovePrivate again, creating a recurring republishing loop.
- The file invokes checkAndRemovePrivate at top level when executed.
Evidence against
- package.json has no install or lifecycle hook, and its scripts only run Next.js commands.
- No package source references autopublish2.js, so the publishing routine is not wired into the declared app entry points or scripts.
Behavioral surface
ChildProcessFilesystemShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
6 flaggedautopublish2.jsView file
1const fs = require('fs');
L2: const { exec } = require('child_process');
L3:
...
L35:
L36: function checkAndRemovePrivate() {
L37: const animation = ['Sedang memeriksa package... ', 'Sedang memeriksa package. ', 'Sedang memeriksa package.. ', 'Sedang memeriksa package...'];
...
L39: const animationInterval = setInterval(() => {
L40: process.stdout.write('\r' + animation[currentFrame]);
L41: currentFrame = (currentFrame + 1) % animation.length;
...
L47: let packageJson = fs.readFileSync('package.json');
L48: let packageData = JSON.parse(packageJson);
L49: 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:
High
•matchType = malicious_source_fingerprint_signature
signature = 41d3d6dd7ce05ed8
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = peas-tea-curut@3.2.2
matchedPath = autopublish2.js
matchedIdentity = npm:cGVhcy10ZWEtY3VydXQ:3.2.2
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 quiche-tea-curut@4.3.4.
See all versions of quiche-tea-curut for other recorded verdicts.
- Avoid installing quiche-tea-curut@4.3.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.