MAL-2026-13237 Malicious code in bigops-products-accounts-and-cards (npm)
Malicious package
Published
MAL-2026-13237 is a malicious package: bigops-products-accounts-and-cards (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-13237/ (Markdown: https://insights.sbomify.com/MAL-2026-13237/index.md)
- Package
- bigops-products-accounts-and-cards
- Registry
- npm
What is MAL-2026-13237?
MAL-2026-13237 is a malicious package in bigops-products-accounts-and-cards, published on 5 Aug 2026.
Official description
On require of this package, index.js loads shim.js which selects a platform-specific binary, downloads it over HTTPS from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev and sibling *.workers.dev endpoints), writes it to a temp path under a disguised filename (dotnet_diag.exe /.cache_), sets it executable via chmodSync 0o755, and detached-spawns it through /bin/sh -c or cmd. A DNS TXT-record base64 channel to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru provides a fallback delivery path. A second fully-formed dropper is shipped as lib/telemetry.js under an 'analytics SDK' cover story, implementing the same base64-assembled payload plus spawn('/bin/sh',['-c', filePath+' &']) pattern with string-concatenated API names (fs['chmod'+'Sync']). Hostnames and dangerous API identifiers are assembled at runtime via array joins to evade static analysis. Any consumer that imports the package receives arbitrary attacker-controlled code execution on their machine.
What should I do about MAL-2026-13237?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.