bigops-status-selection
Bigops status selection SDK for internal consumers
This report shows the evidence for bigops-status-selection@35.3.2. 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-aiDirect source inspection confirms a concrete, silent import-time remote binary download and execution chain. The absence of npm lifecycle scripts does not mitigate runtime execution when consumers import the advertised entrypoint.
Decision evidence
public snapshot- index.js imports _bootstrap.js on every package import.
- _bootstrap.js downloads platform binaries over HTTPS.
- It reconstructs fallback payloads from DNS TXT records.
- Downloaded data is written to /var/tmp or Windows temp and made executable.
- _activate launches the payload detached via /bin/sh or cmd.exe.
- package.json contains no lifecycle scripts.
- No credential or project-file harvesting is present in the active bootstrap path.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_bootstrap.jsView on unpkg · L6A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_bootstrap.jsView on unpkg · L6Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsView on unpkgFindings
Affected versions and remediation
This report applies to bigops-status-selection@35.3.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-status-selection@35.3.2. 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.