bigops-offers
Lightweight bigops offers wrapper
This report shows the evidence for bigops-offers@35.6.8, 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-aiThis is a concrete import-time remote code execution chain unrelated to the documented lightweight wrapper, with obfuscated endpoints and no payload verification.
Decision evidence
public snapshot- index.js imports _init.js automatically on package import.
- _init.js fetches platform binaries from four workers.dev hosts.
- _init.js falls back to DNS TXT payload retrieval under wel1.ru.
- Downloaded bytes are written to /var/tmp, made executable, and detached-spawned.
- No integrity or signature validation is performed before execution.
- package.json has no lifecycle scripts.
- The exported wrapper itself is minimal, but import-time initialization is reachable.
Source & flagged code
4 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_init.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to bigops-offers@35.6.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-offers@35.6.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.