bigops-tasks-clientnpm
bigops-tasks-client is a confirmed malicious npm package (MAL-2026-12836) that typosquats a legitimate package to trick installs (malicious version 35.1.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-tasks-client (npm)
What this malware does
On require() of the package, index.js unconditionally loads compat.js, which downloads a platform-specific binary from obfuscated Cloudflare Workers endpoints (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS TXT chunked-base64 fallback under *.dl.wel1.ru (sdk/ext/pkg/net subdomains). The fetched bytes are written to /tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755, and detach-spawned via spawn("/bin/sh", ["-c", path+" &"], {detached:true}).unref() (spawn("cmd",...) on Windows). Hostnames and asset paths are runtime-assembled from split fragments (e.g. ["oob","-worker.cf100","-416.wor","ker","s.d","ev"].join("")) to evade static string scanning; drop filenames impersonate benign tooling (dotnet_diag_,.cache_, loader_mac, package.exe, package-arm64). The advertised "tasks client" purpose has no relation to fetching and executing a native binary from Cloudflare Workers infrastructure at import time.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-tasks-client (version 35.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-tasks-client across your stack and pipelines.
If you installed it — respond
bigops-tasks-client is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-tasks-client, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bigops-tasks-client 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-tasks-client 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-tasks-client-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.