Malicious code in bigops-customer (npm)
The npm package bigops-customer contains malicious code that downloads and executes platform-specific binaries from hardcoded Cloudflare Workers hosts. The package disguises the behavior as telemetry and uses DNS TXT-record fallback channels to retrieve payloads when HTTPS fails.
- Disclosed
- Last updated
- Blast radius
- Any npm consumer of the bigops-customer package
- Ecosystems
- Attack vectors
- Affected entities
- bigops-customernpm package containing malicious code
The npm package bigops-customer has been identified as containing malicious code. Upon require(), the package's main entry loads a module that downloads platform-specific binaries from hardcoded Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, cf99-9b3.workers.dev, cf102-baf.workers.dev). The URLs are assembled at runtime from split string fragments to evade static analysis.
The fetched binaries are written to temporary directories (/tmp on Unix, %TEMP% on Windows) under disguised names (.cache_ on Unix, dotnet_diag_.exe on Windows), made executable (chmod 0755), and spawned as detached processes via /bin/sh or cmd.exe. No hash or signature verification is performed on the downloaded code.
The package implements a DNS TXT-record fallback mechanism that retrieves payloads when HTTPS fails, using base64-encoded chunks assembled from numbered subdomains. The malicious behavior is framed in code comments as 'telemetry' with opt-out environment variables (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and a cooldown marker (.analytics_state) to control re-execution. The package description ('Bigops customer abstraction layer') is generic and unrelated to the actual code functionality.
The fetched code executes with the privileges of the package installer, and the destinations are anonymous serverless hosts unrelated to any legitimate publisher identity.
Indicators of compromise
- Packages
- bigops-customer
- Domains
- oob-worker.cf103-070.workers.dev
- cf99-9b3.workers.dev
- cf102-baf.workers.dev
Remediation
- Immediately uninstall the bigops-customer package from all environments
- Audit npm install logs to identify all systems that have installed this package
- Review process execution logs on affected systems for suspicious binary execution from /tmp or %TEMP%
- Check for any outbound connections to the identified Cloudflare Workers domains and DNS queries to suspicious subdomains
- Regenerate any credentials or secrets that may have been exposed on affected systems
- Consider the affected systems as potentially compromised and perform full security assessment
- Update npm dependencies to remove bigops-customer and identify legitimate alternatives if needed
Sources
- GitHub Advisory GHSA-8vj2-2pp5-wgw7 · GitHub Advisory Database
Cite this entry
"Malicious code in bigops-customer (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-bigops-customer-npm-6fomt6
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in santana-baileys (npm)
Malicious code discovered in santana-baileys npm package that covertly relays WhatsApp messaging data to an attacker-controlled endpoint (https://fiora.nixel.my.id/) via obfuscated character-code reconstruction in the message-send code path.
npmCompromised package - resolvedcritical
Malicious code in elephant-tusk-runner (npm)
The npm package elephant-tusk-runner contained malicious code that exposed a remote shell and remote code execution surface via an unauthenticated Express + WebSocket server binding to 0.0.0.0:4201 with fully open CORS. Any peer able to reach the port could execute arbitrary commands on the host.
npmCompromised package - resolvedcritical
Malicious code in @cats-cdf/browser-metrics-meter (npm)
The npm package @cats-cdf/browser-metrics-meter contained malicious code in its preinstall lifecycle script that exfiltrated system reconnaissance data (username, hostname, public IP) to an OAST collector domain. The package executed this behavior unconditionally on installation without consent or documented purpose.
npmCompromised package - resolvedcritical
Malicious code in @ks-video/kwai-player-web (npm)
The npm package @ks-video/kwai-player-web contained malicious code in its postinstall hook that exfiltrated system reconnaissance data (hostname, username, working directory, network interfaces, environment variable names) over plain HTTP to an unrelated third-party domain. The package has no legitimate relationship to the declared publisher Kwai/@ks-video.
npmCompromised package