unemployed_xerinae-toolteadev@1.4.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 2h ago · by lpm-firewall-ai`auto.js` contains deliberate package republishing behavior: it changes package identity and publication settings, runs `npm publish`, and repeats. It is not wired to the declared scripts or app entrypoint, so the trigger is explicit execution of that file.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Only when a user or another process explicitly runs `auto.js`; package scripts and app imports inspected do not invoke it by default.
Impact
With valid npm credentials and a package lockfile, it can publish packages under changing names and versions using the user's npm account.
Mechanism
It removes the private flag, changes version and name, rewrites package metadata and lockfile, then runs `npm publish --access public` and schedules another attempt.
Attack narrative
Running `auto.js` alters the current package metadata to make it public, changes its name and version, and publishes it to npm. It then schedules the process to repeat. The reviewed package scripts and app entry code do not call this file automatically, so the behavior requires explicit execution.
AI rationale
`auto.js` contains deliberate package republishing behavior: it changes package identity and publication settings, runs `npm publish`, and repeats. It is not wired to the declared scripts or app entrypoint, so the trigger is explicit execution of that file.
Evidence
auto.jspackage.jsonpackage-lock.json
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- `auto.js` removes `private: true` from the working package metadata, enabling publication.
- When run, `auto.js` changes the package version and name, rewrites `package.json` and `package-lock.json`, and invokes `npm publish --access public`.
- After publishing, `auto.js` schedules the process to repeat, creating a republishing loop.
Evidence against
- The declared npm scripts are ordinary Next.js development, build, start, and lint commands; none invokes `auto.js`.
- The app page is a standard Next.js starter page and does not import `auto.js`.
- The package declares no lifecycle scripts that automatically run this publishing code during installation.
Behavioral surface
ChildProcessFilesystemShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedauto.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.
auto.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 = 45b2b61a8f143289
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = related_blackbird-toolteadev@2.1.1
matchedPath = auto.js
matchedIdentity = npm:[redacted]:2.1.1
similarity = 1.000
shingleOverlap = 2
summary = package final verdict is malicious
Findings
1 Critical7 High4 Low
CriticalNpm Publish Wormauto.js
HighChild Processauto.js
HighShell
HighKnown Malware Source Fingerprint Signatureauto.js
HighAi Review Evidenceauto.js
HighAi Review Evidenceauto.js
HighAi Review Evidenceauto.js
HighAi Review Evidenceauto.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to unemployed_xerinae-toolteadev@1.4.4.
See all versions of unemployed_xerinae-toolteadev for other recorded verdicts.
- Avoid installing unemployed_xerinae-toolteadev@1.4.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.