bigops-telephony-uinpm
bigops-telephony-ui is a confirmed malicious npm package (MAL-2026-12842) that executes malicious code on install (malicious version 35.7.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-telephony-ui (npm)
What this malware does
On require of the package, shim.js downloads a platform-specific executable over HTTPS from string-concatenated hostnames (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adfs.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked fallback to sdk.dl.wel1.ru and sibling *.dl.wel1.ru subdomains. The retrieved bytes are written to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755, and spawned detached via spawn("/bin/sh", ["-c",...]) or spawn("cmd",...). Host strings and the require("child_process") / fs.chmodSync API names are reassembled at runtime via array.join("") to defeat static inspection. The advertised purpose is a React UI component library; nothing about the fetched binary, the decoy filenames, or the anonymous Cloudflare Workers / DNS-fallback delivery matches that stated purpose.
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-telephony-ui (version 35.7.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-telephony-ui across your stack and pipelines.
If you installed it — respond
Remove bigops-telephony-ui 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-telephony-ui 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-telephony-ui 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-telephony-ui-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.