Which versions of bigops-communication-client are malicious?

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

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

bigops-communication-client is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-communication-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-communication-client — how do I know if it already compromised me?

If bigops-communication-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-communication-client part of a known attack campaign?

Yes — bigops-communication-client is associated with the IN-MAL-2026-014408 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-communication-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-communication-client (version 35.8.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-communication-client across your stack and pipelines.

Malicious package

bigops-communication-clientnpm

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

Malicious code in bigops-communication-client (npm)

MAL-2026-12161

Immediate action

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

npm uninstall bigops-communication-client

What this malware does

On require() of the package, index.js loads platform.js which invokes init() at module top level. init() downloads an opaque binary from Cloudflare Workers subdomains (oob-worker.cf102-baf.workers.dev, cf100-416, cf103-070, cf99-9b3.workers.dev) whose hostnames are reconstructed at runtime via array-join to evade static string scanners, with a DNS TXT covert channel (chunked base64 payload retrieved from sdk.dl.wel1.ru) as fallback. The fetched bytes are written to /tmp or %TEMP% under names impersonating.NET diagnostic tools (dotnet_diag<tag>.exe,.cache_<tag>), chmod 0755 on Unix, then spawned detached via /bin/sh -c or cmd.exe start /b with stdio ignored. Anti-analysis logic aborts execution if DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK are set and stamps /tmp/.analytics_state to skip re-execution for ~22438 seconds, framing the dropper as telemetry. There is no legitimate purpose for a require()-time fetch-and-execute of an unpinned, unverified binary from anonymous Workers hosts with runtime host reconstruction and a DNS-TXT payload channel.

Malicious versions

1 flagged

35.8.8

Indicators of compromise (SHA-256)

81c94eee2da1d74fc50236452fc79165eb1183ce0bb874a62a9a7985b6e77206

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-communication-client (version 35.8.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-communication-client across your stack and pipelines.
If you installed it — respond
bigops-communication-client is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-communication-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-communication-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-communication-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-communication-client on npm has been identified as a malicious package (version 35.8.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014408

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-communication-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