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

bigops-apinpm

Advisory published Updated

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.

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

1 flagged
35.8.8

Indicators of compromise (SHA-256)

49069c4e461f88725c6657a31565110fba41d9fa5525d9683d071614ceb6f7f6
0f38974f54013eec7b7aeed64789e4408ff9e2a18a73dd7b04fafe493d57fd89

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bigops-api (version 35.8.8).

  2. 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.

  3. Did it already run?

    If bigops-api 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-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-015550GHSA-fpj4-wwp3-6693

References

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.

Explore

bigops-api (npm) malicious package — MAL-2026-12832 | O3 Security