ratelimitsucks5
Republished package
This report shows the evidence for ratelimitsucks5@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-aiThis is not a normal executable npm library: its HTML entry silently imports unrelated remote code and establishes browser interception/proxy infrastructure. The absence of install hooks does not mitigate the runtime remote-code execution path.
Decision evidence
public snapshot- `index.html` automatically loads unpinned remote code from `https://c.vipersfutbol.com/script.js`.
- `assets/index-CJm_PfL2.js` is heavily obfuscated and constructs code with `new Function(...)`.
- `assets/boot-CVPGRFHh.js` registers `j6k3y8.js` as a service worker at runtime.
- `j6k3y8.js` and `ct1tl/jmqwjq.js` claim clients and intercept routed fetch requests.
- `assets/boot-CVPGRFHh.js` configures a proxy WebSocket endpoint at `wss://21baseballacademy.com/fairs/`.
- No package lifecycle hook is needed: opening the declared HTML entry triggers the remote loader.
- `package.json` contains no `preinstall`, `install`, `postinstall`, or `prepare` scripts.
- No Node filesystem, shell, environment-harvesting, or native executable usage was found in inspected sources.
- The bundled proxy/service-worker code has an apparent web-proxy purpose, but it does not justify the unrelated remote script loader.
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 ratelimitsucks5@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing ratelimitsucks5@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.