MAL-2026-13230 Malicious code in bigops-operator-status (npm)
Malicious package
Published
MAL-2026-13230 is a malicious package: bigops-operator-status (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-13230/ (Markdown: https://insights.sbomify.com/MAL-2026-13230/index.md)
- Package
- bigops-operator-status
- Registry
- npm
What is MAL-2026-13230?
MAL-2026-13230 is a malicious package in bigops-operator-status, published on 5 Aug 2026.
Official description
On require() of this package, index.js loads support.js which selects a platform-specific asset path (linux/darwin/windows), fetches a binary payload from one of four Cloudflare Workers hostnames whose strings are assembled at runtime from split arrays to evade static analysis (oob-worker.cf102-baf.workers.dev, cf99-9b3, cf103-070, cf101-adf), writes the bytes to a disguised path under /tmp or the Windows Temp directory (e.g. dotnet_diag.exe,.cache_), chmods 0755, and spawns the resulting binary detached via /bin/sh -c or cmd. If HTTPS retrieval fails, _support.js falls back to a DNS-TXT covert channel under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru: it resolves c.<domain> for a chunk count, then queries 0.<domain>..N.<domain>, base64-decodes the concatenated TXT contents into a binary, and executes it the same way. The destinations are not publisher-controlled, the payload bytes are opaque, and the hosts are obfuscated by string splitting — the shape is a full-host remote code execution dropper triggered at module load.
What should I do about MAL-2026-13230?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.