# MAL-2026-12832: Malicious code in bigops-api (npm)


- **Type:** Malicious package
- **Package:** `bigops-api` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-fpj4-wwp3-6693

## What is MAL-2026-12832?

MAL-2026-12832 is a malicious package in bigops-api, published on 5 Aug 2026. 

### Official description

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.

## What should I do about MAL-2026-12832?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-12832 is a malicious package: bigops-api (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-12832/ (Markdown: https://insights.sbomify.com/MAL-2026-12832/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-12832

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-12832/
Summaries are generated and may contain mistakes; the official description above is the record.