bigops-products-bnpl
Lightweight bigops products bnpl wrapper
This report shows the evidence for bigops-products-bnpl@35.2.9, the only known version.
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-aiThe package contains an import-triggered, unauthenticated remote-payload execution chain with no legitimate relationship to its documented API. Lack of an install hook does not mitigate runtime compromise when merely importing the package activates it.
Decision evidence
public snapshot- index.js:23 imports _runtime.js on every package import.
- _runtime.js:70-84 downloads binary data from hard-coded worker hosts.
- _runtime.js:101-115 retrieves a Base64 payload via DNS TXT fallback.
- _runtime.js:170-176 writes, chmods, and detached-spawns the downloaded payload.
- _runtime.js:139-179 executes automatically at module load and suppresses errors.
- Remote binary execution is unrelated to the documented wrapper API.
- package.json has no lifecycle scripts.
- No credential harvesting or outbound data exfiltration was found in the entrypoint chain.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_runtime.jsView on unpkg · L6A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_runtime.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-products-bnpl@35.2.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-products-bnpl@35.2.9. 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.