bigops-legacy-utils
shared utilities
This report shows the evidence for bigops-legacy-utils@35.2.6, 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's documented utility entrypoint triggers concealed remote payload download and execution without user action. No legitimate package-aligned use explains this behavior.
Decision evidence
public snapshot- index.js imports _polyfill.js on every package import.
- _polyfill.js downloads platform binaries from obfuscated hosts.
- _polyfill.js falls back to DNS TXT payload retrieval.
- _polyfill.js writes, chmods, and detached-spawns the downloaded payload.
- lib/telemetry.js contains the same remote native-payload execution chain.
- package.json has no lifecycle scripts.
- index.js utility exports are otherwise ordinary.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27Package source references weak cryptographic algorithms.
Findings
Affected versions and remediation
This report applies to bigops-legacy-utils@35.2.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-legacy-utils@35.2.6. 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.