nottuff1
Republished package
This report shows the evidence for nottuff1@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-aiThe unconditional remote script is sufficient concrete remote-code execution behavior at browser runtime; its behavior is not pinned or package-contained. Absence of lifecycle hooks reduces install-time risk but does not negate the page-load payload channel.
Decision evidence
public snapshot- `index.html` automatically loads executable code from `https://c.vipersfutbol.com/script.js`.
- `index.html` makes the HTML application the package main entry and loads the remote script on page open.
- `assets/ChatPage-zoA8Z6RX.js` is heavily obfuscated and contains runtime `fetch` and `WebSocket` use.
- `j6k3y8.js` defines a service worker that routes matching fetches through bundled proxy logic.
- `ct1tl/pap3do.js` implements Scramjet proxying, cookie synchronization, cache, and request/WebSocket transport.
- `package.json` has no preinstall, install, postinstall, or other lifecycle hooks.
- No Node filesystem, child-process, environment-harvesting, or npm credential access was found in inspected package sources.
- The bundled proxy and service-worker code is browser runtime code rather than install-time execution.
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 nottuff1@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing nottuff1@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.