pearx93qja-notthedevs@1.1.8
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 bundled script performs repeated, unsolicited public npm publishing under the current account, after changing local package metadata. Although it is not wired to run on install or import, its concrete publishing loop is malicious when executed.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Directly running autochange2.js; the package manifest does not wire it to an npm lifecycle script or entry point.
Impact
Can publish unsolicited public packages under the user's npm credentials and repeatedly alter the working package metadata.
Mechanism
The script changes the package name and lockfile, runs npm publish --access public, and schedules another attempt after a random delay.
Attack narrative
If run directly, autochange2.js renames the local package to a random name, updates package.json and package-lock.json, and publishes it publicly with npm. It then schedules another attempt after a random delay, creating a repeated publishing loop using the user's active npm credentials. The manifest does not invoke this script automatically, but its behavior is unrelated to the documented Next.js project.
AI rationale
The bundled script performs repeated, unsolicited public npm publishing under the current account, after changing local package metadata. Although it is not wired to run on install or import, its concrete publishing loop is malicious when executed.
Evidence
autochange2.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 autochange2.js immediately starts the publishing routine; it is not listed as an npm lifecycle script.
- The routine replaces the package name with a random name ending in -notthedevs and writes the change to package.json and package-lock.json.
- It invokes npm publish --access public, then schedules another publishing attempt after a random delay.
- The package manifest lists only Next.js development, build, start and lint scripts.
Evidence against
- The manifest declares no install lifecycle hooks.
- The README describes a Next.js app and directs users to run the development server; it does not describe the publishing script.
Behavioral surface
ChildProcessFilesystemShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
6 flaggedautochange2.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.
autochange2.jsView on unpkg · L11const fs = require('fs');
L2: const { exec } = require('child_process');
L3:
High
64}
publishWithDelay();
High
Suspicious Lifecycle Evidence
Running autochange2.js immediately starts the publishing routine; it is not listed as an npm lifecycle script.
autochange2.jsView on unpkg · L64Findings
1 Critical6 High5 Low
CriticalNpm Publish Wormautochange2.js
HighChild Processautochange2.js
HighShell
HighSuspicious Lifecycle Evidenceautochange2.js
HighAi Review Evidenceautochange2.js
HighAi Review Evidenceautochange2.js
HighAi Review Evidencepackage.json
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to pearx93qja-notthedevs@1.1.8.
See all versions of pearx93qja-notthedevs for other recorded verdicts.
- Avoid installing pearx93qja-notthedevs@1.1.8. 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.