peas-tea-curut@3.2.2
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-aiThe package contains a script that mutates package metadata and repeatedly publishes the current project publicly under generated names using the configured npm credentials. Although the manifest does not invoke it automatically, the script is a concrete publishing abuse mechanism unrelated to the package's stated app purpose.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Running autopublish2.js.
Impact
It can publish the user's package contents under generated public names using the npm account and registry configured in the environment.
Mechanism
It edits package metadata, assigns a generated package name, then runs `npm publish --access public` and schedules another attempt.
Attack narrative
When run, autopublish2.js repeatedly changes the current package name and version, makes a package marked private public, and publishes it with the configured npm account. It schedules further publish attempts, so invoking the script can turn the user's package and npm access into a repeated public publishing mechanism. The package manifest does not invoke this script automatically, but the script's behavior is explicit and unrelated to the package's stated Next.js app purpose.
AI rationale
The package contains a script that mutates package metadata and repeatedly publishes the current project publicly under generated names using the configured npm credentials. Although the manifest does not invoke it automatically, the script is a concrete publishing abuse mechanism unrelated to the package's stated app purpose.
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 renames the package to a randomly selected fruit-tea name and writes the change to package.json and package-lock.json.
- The script invokes `npm publish --access public`, using the npm CLI's configured credentials and registry.
- The script starts its publishing chain when run and schedules another publishing attempt after each publish.
Evidence against
- package.json defines only Next.js development, build, start, and lint scripts; it does not wire autopublish2.js to a package lifecycle or command.
- The inspected arts-dao dependency entry point contains ordinary in-memory DAO methods.
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 = quiche-tea-curut@4.3.4
matchedPath = autopublish2.js
matchedIdentity = npm:cXVpY2hlLXRlYS1jdXJ1dA:4.3.4
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 peas-tea-curut@3.2.2.
See all versions of peas-tea-curut for other recorded verdicts.
- Avoid installing peas-tea-curut@3.2.2. 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.