bigops-operator-status (npm) · Malicious Code
Affects bigops-operator-statusSource GCVE Database
Malicious package : remove bigops-operator-status and rotate any secrets on hosts that installed it.
Data as of 5 Aug 2026, 22:46 UTC
Malicious package
Published to npm · OSV MAL-2026-13230
What to do
Remove bigops-operator-status from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmbigops-operator-status | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The bigops-operator-status npm package version 35.4.5 contains malicious code that, upon being required, downloads and executes a platform-specific binary payload from obfuscated Cloudflare Workers hostnames or, if that fails, via a DNS-TXT covert channel. This payload is written to temporary directories, made executable, and run detached, enabling remote code execution. The payload sources are not controlled by the package publisher, and the binary content is opaque, indicating a fully functional remote code execution dropper triggered at module load.