nottuff12
This report shows the evidence for nottuff12@2.0.0. 3 of 3 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10339 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The package contains a concrete automatic remote-code and traffic-interception surface when its HTML entrypoint is opened. That behavior is high risk and materially unrelated to a normal npm package, but it is not install-time host malware.
Independent scan evidence
public snapshot- `index.html` automatically loads `https://c.vipersfutbol.com/script.js`.
- `assets/boot-CVPGRFHh.js` registers `j6k3y8.js` as a service worker.
- `j6k3y8.js` claims clients and routes every matching fetch through `_19vij0x.route`.
- `assets/boot-CVPGRFHh.js` configures a proxy transport to `wss://21baseballacademy.com/fairs/`.
- `ct1tl/pap3do.js` proxy code rewrites requests and syncs cookies.
- `package.json` has no `preinstall`, `install`, `postinstall`, or other lifecycle scripts.
- `main` is `index.html`; install does not automatically execute browser assets.
- No inspected source showed child-process use, local credential-file harvesting, or AI-agent configuration writes.
Source & flagged code
7 flagged · loading sourcePackage contains a critical-looking secret pattern.
assets/proxy-runtime-1NyFshf9.jsView on unpkg · L1AWS access key ID in assets/proxy-runtime-1NyFshf9.js
assets/proxy-runtime-1NyFshf9.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to nottuff12@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing nottuff12@2.0.0. 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.