nottuff30
This report shows the evidence for nottuff30@2.0.0. 3 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10356 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
This is not a conventional npm library: it is an obfuscated browser proxy application with automatic service-worker setup and remote runtime code. The concrete risky capability warrants a warning, while lack of confirmed theft or install-time behavior does not justify a block.
Independent scan evidence
public snapshot- `index.html` executes `https://c.vipersfutbol.com/script.js` at page load.
- `assets/index-CJm_PfL2.js` obfuscates an immediate `bootController()` call.
- `assets/boot-CVPGRFHh.js` registers `j6k3y8.js` as a service worker.
- `j6k3y8.js` claims clients and routes browser fetch events.
- `assets/boot-CVPGRFHh.js` sends proxy traffic to `wss://21baseballacademy.com/fairs/`.
- `ct1tl/pap3do.js` injects proxy hooks and persists proxied cookies.
- `package.json` has no preinstall, install, postinstall, or bin hook.
- No Node child-process, filesystem, or environment harvesting path was found.
Source & flagged code
9 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 nottuff30@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing nottuff30@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.