nottuff24
Republished package
This report shows the evidence for nottuff24@2.0.0. 3 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect source inspection confirms automatic remote-code execution and local obfuscated dynamic execution when the declared HTML entrypoint is opened. Absence of npm lifecycle hooks does not mitigate this runtime attack path.
Decision evidence
public snapshot- `index.html` auto-loads `https://c.vipersfutbol.com/script.js`.
- `assets/index-CJm_PfL2.js` contains an obfuscated base64/decompression loader and `new Function` execution.
- `assets/boot-CVPGRFHh.js` registers `j6k3y8.js` as a service worker.
- `j6k3y8.js` intercepts routed fetches; `ct1tl/` implements proxy/cookie transport.
- No npm lifecycle hook is needed: opening `index.html` triggers the remote script.
- `package.json` has no preinstall/install/postinstall hooks.
- No Node filesystem, shell, or environment-variable harvesting 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 nottuff24@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing nottuff24@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.