nottuff10
Republished package
This report shows the evidence for nottuff10@2.0.0. 3 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiNo install hook executes during npm installation, but the declared browser entrypoint contains a concrete third-party remote-code execution path and an opaque request-interception stack. That is sufficient to block publication as a malicious runtime payload.
Decision evidence
public snapshot- `index.html` loads executable JavaScript from `https://c.vipersfutbol.com/script.js`.
- `index.html` automatically loads proxy and controller bundles on page open.
- `j6k3y8.js` installs a fetch-intercepting service worker.
- `ct1tl/jmqwjq.js` proxies matching requests and relays cookies through controlled clients.
- `assets/ChatPage-zoA8Z6RX.js` is heavily obfuscated, preventing transparent review of its runtime behavior.
- `package.json` has no preinstall, install, postinstall, or other lifecycle hook.
- No Node filesystem, shell, credential-harvesting, or package-install-time execution was found in inspected entry files.
- Font blobs and the local WASM module are consistent with the shipped browser proxy application.
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 nottuff10@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing nottuff10@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.