dian-peyek23-miaww@1.1.3
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 4h ago · by lpm-firewall-aiThe package includes a standalone script that repeatedly renames and republishes the project to npm, an unrelated self-propagation behavior. It is not wired to normal installation or the manifest’s scripts, so execution requires running auto.js directly.
Static reason
High-risk behavior combination matched malicious policy.; source fingerprint signature matched known malicious package; routed for review
Trigger
Direct execution of auto.js; the manifest does not invoke it during install or through its declared scripts.
Impact
An unsuspecting user who runs the script may publish packages using their npm authorization and enable repeated propagation.
Mechanism
The script edits package.json and package-lock.json, runs `npm publish --access public`, then schedules another publishing cycle.
Attack narrative
If run directly, auto.js changes the package name and version, publishes it publicly with npm, then schedules another cycle. The manifest does not trigger it through installation or its declared scripts, but the bundled publishing routine is unrelated to the Next.js project and could misuse the runner’s npm publishing authorization.
AI rationale
The package includes a standalone script that repeatedly renames and republishes the project to npm, an unrelated self-propagation behavior. It is not wired to normal installation or the manifest’s scripts, so execution requires running auto.js directly.
Evidence
auto.jspackage.jsonpackage-lock.json
Decision evidence
public snapshotAI called this Malicious at 95.0% confidence as Malware with low false-positive risk.
Evidence for block
- The manifest declares only Next.js development, build, start, and lint scripts; it does not wire auto.js to a package lifecycle or entry point.
- When executed directly, auto.js starts its publishing routine and changes the package version and name.
- The script runs `npm publish --access public` and schedules the routine to repeat after a delay.
Evidence against
- The manifest contains no install lifecycle scripts, and the publishing behavior is not triggered by the declared package scripts.
Behavioral surface
ChildProcessFilesystemShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
6 flaggedauto.jsView file
1const fs = require('fs');
L2: const { exec } = require('child_process');
L3:
...
L21:
L22: function checkAndRemovePrivate() {
L23: const animation = ['Sedang memeriksa package... ', 'Sedang memeriksa package. ', 'Sedang memeriksa package.. ', 'Sedang memeriksa package...'];
...
L25: const animationInterval = setInterval(() => {
L26: process.stdout.write('\r' + animation[currentFrame]);
L27: currentFrame = (currentFrame + 1) % animation.length;
...
L33: let packageJson = fs.readFileSync('package.json');
L34: let packageData = JSON.parse(packageJson);
L35: 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:
High
•matchType = malicious_source_fingerprint_signature
signature = ef57d1bb402cfb5b
signatureType = suspicious_hashes
sourceLabel = Datadog
matchedPackage = agus-tongseng59-breki@4.4.2
matchedPath = auto.js
matchedIdentity = npm:YWd1cy10b25nc2VuZzU5LWJyZWtp:4.4.2
similarity = 1.000
shingleOverlap = 2
summary = Datadog malicious npm corpus sample: samples/npm/malicious_intent/agus-tongseng59-breki/4.4.2/2024-05-13-agus-tongseng59-breki-v4.4.2.zip
Findings
1 Critical6 High5 Low
CriticalNpm Publish Wormauto.js
HighChild Processauto.js
HighShell
HighKnown Malware Source Fingerprint Signatureauto.js
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidenceauto.js
HighAi Review Evidenceauto.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to dian-peyek23-miaww@1.1.3.
See all versions of dian-peyek23-miaww for other recorded verdicts.
- Avoid installing dian-peyek23-miaww@1.1.3. 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.