Which versions of bigops-telephony-client are malicious?

The following npm versions of bigops-telephony-client are flagged malicious: 35.7.6. Treat any of these as compromised.

How do I remediate bigops-telephony-client if I installed it?

bigops-telephony-client is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-telephony-client, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed bigops-telephony-client — how do I know if it already compromised me?

If bigops-telephony-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.

Is bigops-telephony-client part of a known attack campaign?

Yes — bigops-telephony-client is associated with the IN-MAL-2026-015531 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bigops-telephony-client across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-telephony-client (version 35.7.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-telephony-client across your stack and pipelines.

Malicious package

bigops-telephony-clientnpm

bigops-telephony-client is a confirmed malicious npm package (MAL-2026-12841) that typosquats a legitimate package to trick installs (malicious version 35.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-telephony-client (npm)

MAL-2026-12841

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bigops-telephony-client

What this malware does

On require() of bigops-telephony-client, index.js loads./runtime.js, which unconditionally downloads a platform-specific binary over HTTPS from Cloudflare Workers hosts whose domains are reconstructed by joining split string fragments (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev). The downloaded bytes are written to a disguised location under /tmp or %TEMP% (e.g..cache<rand>, dotnet_diag_<rand>.exe mimicking a.NET diagnostic tool), chmod 0755, and spawned detached via /bin/sh -c or cmd /c start. A fallback code-delivery channel resolves DNS TXT records at sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, using 'c.<domain>' to obtain a chunk count and '0.<domain>'..'N.<domain>' to reassemble a base64-encoded payload. lib/telemetry.js ships a parallel drop-and-execute implementation (WorkerHost/NativeProfiler under an 'Analytics SDK' cover story) with the same primitives, currently unreferenced by the main entry. The combination of split-string domain construction, DNS-TXT covert channel, disguised drop paths, detached spawn, and duplicate loader is a supply-chain dropper delivering arbitrary attacker-controlled code to every consumer.

Malicious versions

1 flagged

35.7.6

Indicators of compromise (SHA-256)

98fd12faa59a5e65d0383cfb3be55ccd49beca5c74cb350b62f5717be83bcd65

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-telephony-client (version 35.7.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-telephony-client across your stack and pipelines.
If you installed it — respond
bigops-telephony-client is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-telephony-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-telephony-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-telephony-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

No. bigops-telephony-client on npm has been identified as a malicious package (version 35.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015531

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-telephony-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database