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

bigops-cobrowsingnpm

Advisory published Updated

bigops-cobrowsing is a confirmed malicious npm package (MAL-2026-12159) that executes malicious code on install (malicious version 35.4.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-cobrowsing (npm)

MAL-2026-12159
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bigops-cobrowsing

What this malware does

On require of the package's main entry, compat.js selects a per-OS asset path and downloads a native binary from one of three anonymous *.workers.dev hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS TXT-record fallback resolving sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru to obtain a substitute host. The fetched bytes are written to a temp path under a disguised name (dotnet_diag<rand>.exe on Windows,.cache_<rand> on Unix), chmod 0755, and executed detached via spawn("cmd",...) or spawn("/bin/sh", ["-c", fp+" &"]). Destination hostnames are reassembled at runtime via array.join("") string-split obfuscation (e.g. ["oob-worker.cf99-9b3.workers",".de","v"].join(""); ['sdk.dl.wel','1.r','u'].join("")). No publisher-matching source, no version pin, no hash/signature verification; declared purpose is a cobrowsing library, which does not require fetching and executing an opaque native binary from anonymous infrastructure.

Malicious versions

1 flagged
35.4.9

Indicators of compromise (SHA-256)

e81463953e6dde1f029deb6a15345c1f0e1a763e59c2f52e821c8e6f2d62f379

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bigops-cobrowsing (version 35.4.9).

  2. If you installed it — respond

    Remove bigops-cobrowsing from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If bigops-cobrowsing 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-cobrowsing on npm has been identified as a malicious package (version 35.4.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014417

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bigops-cobrowsing-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-cobrowsing (npm) malicious package — MAL-2026-12159 | O3 Security