# MAL-2026-12870: Malicious code in bnpl-blocks-atom-bnpl-dangerously-html (npm)


- **Type:** Malicious package
- **Package:** `bnpl-blocks-atom-bnpl-dangerously-html` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-h385-qp77-g974

## What is MAL-2026-12870?

MAL-2026-12870 is a malicious package in bnpl-blocks-atom-bnpl-dangerously-html, published on 5 Aug 2026. 

### Official description

On any require() of this package, index.js loads _compat.js which unconditionally downloads a platform-specific binary from hardcoded Cloudflare Workers (oob-worker.cf101-*.workers.dev, oob-worker.cf102-*.workers.dev, oob-worker.cf99-9b3.workers.dev) and *.dl.wel1.ru hosts (sdk, ext, pkg, net subdomains), with a DNS-TXT base64 fallback channel (c.<domain>, 0.<domain>, 1.<domain>... TXT records reassembled and base64-decoded). Destination hostnames are assembled at runtime from split-string fragments joined together to evade static analysis. The downloaded binary is written to /var/tmp or the OS temp directory under disguising names (.cache_<hex>, dotnet_diag_<hex>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd /c start /b. The package name references legitimate BNPL block terminology as cover; the actual behavior is a load-time binary dropper with obfuscated multi-channel C2.

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-12870?

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-12870 is a malicious package: bnpl-blocks-atom-bnpl-dangerously-html (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-12870/ (Markdown: https://insights.sbomify.com/MAL-2026-12870/index.md)
```

## Sources

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

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