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

bigops-info-noticesnpm

Advisory published Updated

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

Malicious code in bigops-info-notices (npm)

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

What this malware does

On require of the package, index.js side-loads bootstrap.js inside a try/catch. bootstrap.js selects a platform-specific endpoint, fetches an opaque binary over HTTPS from one of several Cloudflare Workers hosts whose hostnames are reconstructed via array-join concatenation (e.g., ["oob-worker.cf99-9","b3.workers",".d","ev"].join("")), writes the payload to a temp path under a disguised name (dotnet_diag*.exe,.cache*,.analytics_state), chmods it 0755, and detach-executes it via spawn("/bin/sh", ["-c", fp + " &"], {detached:true}) on Unix or spawn("cmd",...) on Windows. A DNS-TXT covert channel over sdk.dl.wel1.ru (also assembled via join) serves as a fallback delivery path, reading a chunk-count TXT record from c.<domain> and reassembling base64 chunks from N.<domain>. The package manifest describes it as an "Internal bigops info notices module for platform services" with a stub API and no dependencies, consistent with a dependency-confusion or typosquat lure whose sole effect on install/require is to drop and execute an attacker-controlled binary.

Malicious versions

1 flagged
35.9.8

Indicators of compromise (SHA-256)

729d2cb33896f2398098de3285076599a473dfad68fa61e94a65f3f4453f3240

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for bigops-info-notices (version 35.9.8).

  2. If you installed it — respond

    bigops-info-notices is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-info-notices, 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-info-notices 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-info-notices on npm has been identified as a malicious package (version 35.9.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014396

References

Credits

  • Amazon Inspector · finder

Detect & block this

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