speed2
Republished package
This report shows the evidence for speed2@2.0.0. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is not an inert library artifact: its entrypoint executes remote, operator-controlled code and includes browser request-interception infrastructure. Absence of npm lifecycle hooks does not mitigate runtime remote payload execution.
Decision evidence
public snapshot- `index.html` loads and executes remote `https://c.vipersfutbol.com/script.js`.
- `index.html` loads local `bfjdx/757lr8.js` and `ct1tl/pap3do.js` before the application bundle.
- `j6k3y8.js` installs a service worker that intercepts matching fetches.
- `ct1tl/jmqwjq.js` routes intercepted requests through a controller and relays cookies.
- `assets/ChatPage-zoA8Z6RX.js` is deliberately obfuscated, hindering audit.
- `package.json` has no npm lifecycle hooks.
- No Node child-process, local credential-file, or environment harvesting was confirmed.
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 speed2@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing speed2@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.