nottuff8
This report shows the evidence for nottuff8@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-10359 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
No install-time Node compromise was found, but the shipped entrypoint creates a concrete externally controlled browser payload path and a proxying control surface. This warrants a warning rather than a block because the remote script's malicious behavior is not established from package source alone.
Independent scan evidence
public snapshot- `index.html` loads executable remote script `https://c.vipersfutbol.com/script.js`.
- `assets/boot-CVPGRFHh.js` registers bundled service worker `j6k3y8.js`.
- `assets/boot-CVPGRFHh.js` contains `wss://21baseballacademy.com/fairs/`.
- `j6k3y8.js` and `ct1tl/jmqwjq.js` intercept routed browser fetches and relay requests.
- `assets/ChatPage-zoA8Z6RX.js` and `assets/index-CJm_PfL2.js` are deliberately obfuscated.
- `package.json` has no npm lifecycle scripts.
- No Node filesystem, subprocess, or environment-harvesting path was confirmed.
- No package-local credential exfiltration payload was confirmed from inspected source.
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 nottuff8@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing nottuff8@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.