related_blackbird-toolteadev@2.1.1
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-ai`auto.js` contains a concrete self-republishing routine that can publish the user’s project publicly under generated package names and repeat the publication. It is not wired into the manifest’s normal scripts or lifecycle, but the unrelated package ships the routine as executable source.
Decision evidence
public snapshot- When `auto.js` runs, it reads and edits the current directory’s package.json, removing `private: true`.
- The script changes the package version and generates a new package name, then runs `npm publish --access public`.
- After publishing, it schedules the process to repeat; an unguarded top-level call starts it when the file is run.
- The manifest defines only standard Next.js scripts and does not wire `auto.js` into a lifecycle hook, bin, or package entry point.
Source & flagged code
6 flaggedSource mutates package metadata and republishes itself to npm.
auto.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to related_blackbird-toolteadev@2.1.1.
See all versions of related_blackbird-toolteadev for other recorded verdicts.
- Avoid installing related_blackbird-toolteadev@2.1.1. 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.