What does the bigops-api malware do?

On require('bigops-api'), index.js loads _compat.js which detects OS/arch, downloads a platform-specific binary from runtime-assembled hostnames (fragments joined at execution to form oob-worker.cf102-baf.workers.dev and sdk.dl.wel1.ru, with DNS-TXT chunked fallback), writes it to a temp path masquerading as a Microsoft diagnostic tool (Windows: dotnet_diag_ .exe; Unix:.cache_ under /var/tmp), chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start /b. No signature or hash verification is performed. A secondary bundled module lib/telemetry.js (~81 KB, presented as an analytics SDK with a DISABLE_TELEMETRY opt-out) duplicates the same fetch-write-chmod-spawn chain, using r

Which versions of bigops-api are malicious?

The following npm versions of bigops-api are flagged malicious: 35.8.8. Treat any of these as compromised.

How do I remediate bigops-api if I installed it?

Remove bigops-api 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.

I already installed bigops-api — how do I know if it already compromised me?

If bigops-api 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.

Is bigops-api part of a known attack campaign?

Yes — bigops-api is associated with the IN-MAL-2026-015550 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bigops-api across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-api (version 35.8.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-api across your stack and pipelines.

Malicious package

bigops-apinpm

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

Malicious code in bigops-api (npm)

MAL-2026-12832

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bigops-api

What this malware does

On require('bigops-api'), index.js loads compat.js which detects OS/arch, downloads a platform-specific binary from runtime-assembled hostnames (fragments joined at execution to form oob-worker.cf102-baf.workers.dev and sdk.dl.wel1.ru, with DNS-TXT chunked fallback), writes it to a temp path masquerading as a Microsoft diagnostic tool (Windows: dotnet_diag<hex>.exe; Unix:.cache_<hex> under /var/tmp), chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start /b. No signature or hash verification is performed. A secondary bundled module lib/telemetry.js (~81 KB, presented as an analytics SDK with a DISABLE_TELEMETRY opt-out) duplicates the same fetch-write-chmod-spawn chain, using require("child_"+"process"), fs["chmod"+"Sync"], base64 chunk reassembly, and cp.spawn("/bin/sh", ["-c", filePath + " &"]). Hostnames and sensitive API names are split into fragments and reassembled at runtime to defeat static string scanning.

Malicious versions

1 flagged

35.8.8

Indicators of compromise (SHA-256)

49069c4e461f88725c6657a31565110fba41d9fa5525d9683d071614ceb6f7f6

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-api (version 35.8.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-api across your stack and pipelines.
If you installed it — respond
Remove bigops-api 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-api 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-api 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

No. bigops-api on npm has been identified as a malicious package (version 35.8.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015550

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-api-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database