bigops-utilsnpm
bigops-utils is a confirmed malicious npm package (MAL-2026-12853) that executes malicious code on install (malicious version 35.4.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-utils (npm)
What this malware does
Loading the package's main entry point auto-invokes helpers.js init(), which downloads an OS-specific binary from obfuscated Cloudflare Workers subdomains (hostnames assembled at runtime from split-string arrays such as MIRRORS=['oob-worker.cf102-baf.w','orke','rs.','de','v'].join('')) with a DNS-TXT chunked fallback that reassembles base64 chunks from TXT records under *.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under deceptive names ('.cache<rand>', 'dotnet_diag<rand>.exe'), chmod'd 0755, and detached-spawned via spawn('/bin/sh', ['-c', fp+' &'], {detached:true}) or cmd.exe /c start /b. No hash or signature verification is performed and the destinations are not tied to any advertised publisher. Sibling lib/telemetry.js uses dynamic API construction (require('child_'+'process'), fs['chmod'+'Sync']) to further evade static analysis. The behavior is framed as 'analytics/telemetry' but is an import-time remote-code dropper.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-utils (version 35.4.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-utils across your stack and pipelines.
If you installed it — respond
Remove bigops-utils 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.
Did it already run?
If bigops-utils 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-utils 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-utils-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.