MAL-2026-13238 Malicious code in bigops-products-bnpl (npm)
Malicious package
Published
MAL-2026-13238 is a malicious package: bigops-products-bnpl (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-13238/ (Markdown: https://insights.sbomify.com/MAL-2026-13238/index.md)
- Package
- bigops-products-bnpl
- Registry
- npm
What is MAL-2026-13238?
MAL-2026-13238 is a malicious package in bigops-products-bnpl, published on 5 Aug 2026.
Official description
On
require('bigops-products-bnpl'), index.js loads runtime.js, which selects a platform-specific endpoint and downloads an opaque binary from one of four hardcoded Cloudflare Workers hosts (oob-worker.cf101-.workers.dev, oob-worker.cf102-.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT base64 fallback via *.dl.wel1.ru. The downloaded bytes are written under a disguised name (e.g. dotnet_diag.exe,.cache_) to /tmp or %TEMP%, chmod'd 0o755, and spawned detached via /bin/sh -c or cmd.exe. Destination hostnames are assembled from split string fragments joined with.join('') to evade static analysis, and a.analytics_state marker file is written to avoid re-running. No hash or signature verification is performed, the hosts are anonymous mutable Cloudflare Workers unrelated to the package's stated 'bnpl wrapper' purpose, and comments frame the code as 'telemetry'/'CDN'/'analytics' as cover. The result is arbitrary attacker-controlled code execution on the installer's machine as a side effect of loading the package.What should I do about MAL-2026-13238?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.