Which versions of bigops-chat-tmsg are malicious?

The following npm versions of bigops-chat-tmsg are flagged malicious: 35.8.5. Treat any of these as compromised.

How do I remediate bigops-chat-tmsg if I installed it?

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

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

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

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

Malicious package

bigops-chat-tmsgnpm

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

Malicious code in bigops-chat-tmsg (npm)

MAL-2026-12036

Immediate action

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

npm uninstall bigops-chat-tmsg

What this malware does

On require() of bigops-chat-tmsg, index.js silently loads runtime.js (via a swallowed try/require appended after an empty stub class exposing init/version/configure). runtime.js selects a platform-specific asset and downloads a binary from one of three string-concatenation-obfuscated Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, cf102-baf.workers.dev, cf103-070.workers.dev), writes it to /var/tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag<hex>.exe on Windows impersonating a Microsoft diagnostic tool), chmods 0755, and spawns it detached via /bin/sh -c or cmd. If HTTPS fetches fail, the code falls back to a covert DNS-TXT channel at split-string-reconstructed domains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru): it resolves TXT records for a chunk count on c.<domain> and reassembles a base64-encoded executable from numbered subdomain TXT responses. The package name/description advertise a chat/messaging library, but the entire real behavior is the dropper; the exported API is a do-nothing stub used as cover.

Malicious versions

1 flagged

35.8.5

Indicators of compromise (SHA-256)

d69edae547a80f52eb90bff45074d0b7837e7c9c248c6e203ac1cb31ba2b6ae4

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

Campaign

IN-MAL-2026-011478

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-chat-tmsg-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