captainindia
Republished package
This report shows the evidence for captainindia@2.0.0. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe direct external script tag is an immediate, unpinned remote payload loader, not merely an inert library reference. Combined with automatic service-worker proxy setup and pervasive obfuscation, it establishes concrete malicious browser-runtime behavior.
Decision evidence
public snapshot- `index.html` immediately executes remote `https://c.vipersfutbol.com/script.js`.
- `assets/boot-CVPGRFHh.js` registers `j6k3y8.js` as a service worker.
- `j6k3y8.js` imports `ct1tl/jmqwjq.js` and intercepts routed fetch events.
- `assets/ChatPage-zoA8Z6RX.js` and `assets/index-CJm_PfL2.js` are heavily obfuscated browser application bundles.
- `ct1tl/pap3do.js` and `bfjdx/757lr8.js` implement Scramjet request, cookie, and WebSocket proxying.
- `package.json` has no npm lifecycle scripts.
- No Node filesystem, shell, environment-harvesting, or install-time execution was found.
- The shipped WASM/proxy components are browser-side rather than native install payloads.
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 captainindia@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing captainindia@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.