bigops-api
REST client wrapper
This report shows the evidence for bigops-api@35.8.8. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete import-time remote-code-execution chain, not ordinary telemetry: fetched executable bytes are launched without validation. Lack of an install hook does not mitigate the reachable runtime execution.
Decision evidence
public snapshot- index.js imports _compat.js at package import time.
- _compat.js downloads platform binaries from obfuscated Workers hosts.
- _compat.js falls back to DNS TXT payload retrieval.
- Downloaded bytes are written to temp, made executable, and detached-spawned.
- No integrity/signature validation precedes execution.
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the entrypoint.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_compat.jsView on unpkg · L2A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_compat.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to bigops-api@35.8.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-api@35.8.8. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.