nottuff5
Republished package
This report shows the evidence for nottuff5@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-aiNo install-time hook exists, but the shipped entrypoint directly executes unpinned remote code and installs a browser request-interception proxy that forwards request data to an unrelated host. These are concrete attack behaviors, not merely bundled-library indicators.
Decision evidence
public snapshot- `index.html` loads remote code from `https://c.vipersfutbol.com/script.js`.
- `assets/boot-CVPGRFHh.js` registers `j6k3y8.js` as a service worker.
- `j6k3y8.js` claims clients and routes matching fetch events.
- `assets/boot-CVPGRFHh.js` configures a request-rewriting proxy over `wss://21baseballacademy.com/fairs/`.
- `ct1tl/jmqwjq.js` forwards intercepted request URL, headers, body, and referrer through its controller RPC.
- `package.json` contains no preinstall, install, postinstall, or other lifecycle hooks.
- Inspected code is browser-only; no Node shell, filesystem, environment, or credential-harvesting APIs were found in the entry flow.
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 nottuff5@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing nottuff5@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.