bigops-call-historynpm
bigops-call-history is a confirmed malicious npm package (MAL-2026-12154) that executes malicious code on install (malicious version 35.8.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-call-history (npm)
What this malware does
The package's index.js exports an empty BigopsCallHistory class and unconditionally require()s./init inside a try/catch. On any require or import, init.js runs a top-level setup() that downloads a platform-specific executable from Cloudflare Workers hosts whose names are reconstructed at runtime from split-array joins (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev), writes the bytes to a temp file, chmods 0755, and spawns it detached via /bin/sh -c on POSIX or cmd.exe /c start /b on Windows. If HTTPS mirrors fail, a resolveDns() routine queries TXT records under *.dl.wel1.ru (c.<domain>, then 0.<domain>..N.<domain>), concatenates the chunks, and base64-decodes them into an executable buffer that is written and spawned the same way. The dropped file uses cover-story names (dotnet_diag*.exe,.cache*, analytics_state marker). Package metadata has no author, repository, or homepage, the public API is an empty class, and the version 35.8.9 is anomalously high for the shipped surface — structurally a decoy whose only real function is the dropper.
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-call-history (version 35.8.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-call-history across your stack and pipelines.
If you installed it — respond
Remove bigops-call-history 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-call-history 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-call-history 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-call-history-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.