nottuff2
Republished package
This report shows the evidence for nottuff2@2.0.0. 3 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms immediate third-party remote code loading and a service-worker proxy transport. No install hook is needed for the package to create a harmful runtime attack surface when its declared entrypoint is used.
Decision evidence
public snapshot- `index.html` executes remote `https://c.vipersfutbol.com/script.js` on page load.
- `assets/boot-CVPGRFHh.js` registers `j6k3y8.js` service worker.
- `ct1tl/jmqwjq.js` intercepts routed fetches and forwards request bodies/headers through its controller.
- `assets/boot-CVPGRFHh.js` configures proxy WebSocket `wss://21baseballacademy.com/fairs/`.
- `assets/ChatPage-zoA8Z6RX.js` is heavily obfuscated and implements username/password sign-in requests.
- `package.json` has no npm lifecycle scripts.
- No Node entrypoint or filesystem/child-process harvesting was found.
- The KaTeX font blobs and WASM runtime are consistent with bundled browser assets.
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 nottuff2@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing nottuff2@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.