bigops-api-customernpm
bigops-api-customer is a confirmed malicious npm package (MAL-2026-12833) that executes malicious code on install (malicious version 35.8.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-api-customer (npm)
What this malware does
On require() of bigops-api-customer, index.js loads compat.js which downloads an OS-specific native binary from obfuscated Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback resolver under wel1.ru. Destination hostnames are assembled via array-join string splits (e.g. ["oo","b-worker.cf101-adf.workers",".de","v"].join("")) to defeat static matching. The fetched bytes are written to /tmp or %TEMP% under disguising names such as.cache<hex> and dotnet_diag_<hex>.exe, chmod 0755, and executed detached via spawn("/bin/sh", ["-c", fp + " &"], {detached:true, stdio:"ignore"}).unref() (with a spawn("cmd") branch for Windows). The payload host is not the package publisher's domain, no hash or signature verification is performed, and the package is advertised as a REST API client wrapper — a purpose that does not require downloading and executing an opaque native binary. Additional cover-story features (DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env checks, TTL rate-limit stamp file, randomized server ordering, "analytics"/"telemetry" comments) surround the dropper logic. Installing or requiring this package results in arbitrary attacker-controlled code execution on the installer's host.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-api-customer (version 35.8.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-api-customer across your stack and pipelines.
If you installed it — respond
Remove bigops-api-customer from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If bigops-api-customer was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks bigops-api-customer before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bigops-api-customer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.