NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bigops-chat-tmsgnpm

Advisory published Updated

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
  1. Find it

    Search your lockfiles and build artifacts for bigops-chat-tmsg (version 35.8.5).

  2. 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.

  3. Did it already run?

    If bigops-chat-tmsg was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

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.

Explore

bigops-chat-tmsg (npm) malicious package — MAL-2026-12036 | O3 Security