Which versions of bigops-chats are malicious?

The following npm versions of bigops-chats are flagged malicious: 35.9.6. Treat any of these as compromised.

How do I remediate bigops-chats if I installed it?

bigops-chats establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

Malicious package

bigops-chatsnpm

bigops-chats is a confirmed malicious npm package (MAL-2026-12157) that opens a backdoor for remote access (malicious version 35.9.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-chats (npm)

MAL-2026-12157

Immediate action

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

npm uninstall bigops-chats

What this malware does

On require() of bigops-chats, index.js loads helpers.js which assembles C2 hostnames via array split-join obfuscation (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, with a DNS-TXT fallback under sdk.dl.wel1.ru), fetches a platform-specific binary from those hosts without hash or signature verification, writes it to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods 0755, and spawns it detached via /bin/sh -c or cmd with stdio ignored. A stamp file at /tmp/.analytics_state suppresses re-runs. The staged filename mimics dotnet diagnostic tooling and the behavior is framed as analytics with an env-var opt-out. Hostnames are not publisher-controlled infrastructure and the delivered bytes are opaque and unverifiable.

Malicious versions

1 flagged

35.9.6

Indicators of compromise (SHA-256)

322310cb37baed38193c12087a25e40901a781467fc070c1bf078293ca8586be

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-chats (version 35.9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-chats across your stack and pipelines.
If you installed it — respond
bigops-chats establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bigops-chats 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-chats 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-chats on npm has been identified as a malicious package (version 35.9.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014403

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-chats-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database