nottuff14
Republished package
This report shows the evidence for nottuff14@2.0.0. 3 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is not merely a static hint: direct source inspection confirms an unconditional remote script execution path from the declared entrypoint. The lack of npm lifecycle hooks limits install-time impact but does not remove the concrete browser-time remote-code-execution risk.
Decision evidence
public snapshot- `index.html` unconditionally loads `https://c.vipersfutbol.com/script.js`.
- `index.html` is the declared `main` entrypoint.
- `assets/ChatPage-zoA8Z6RX.js` and `assets/index-CJm_PfL2.js` are heavily obfuscated.
- `ct1tl/pap3do.js` implements proxy/service-worker cookie and request routing.
- `assets/proxy-runtime-1NyFshf9.js` loads a bundled WebAssembly network runtime.
- `package.json` contains no preinstall, install, or postinstall hook.
- No Node filesystem, environment harvesting, or child-process behavior was found in the inspected entry path.
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 nottuff14@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing nottuff14@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.