bigops-info-noticesnpm
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-info-notices (version 35.9.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-info-notices across your stack and pipelines.
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.
Did it already run?
If bigops-info-notices 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-info-notices 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
Campaign
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.