# MAL-2026-12875: Malicious code in bnpl-blocks-atom-bnpl-feedback (npm)


- **Type:** Malicious package
- **Package:** `bnpl-blocks-atom-bnpl-feedback` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-23mh-5c53-jxhh

## What is MAL-2026-12875?

MAL-2026-12875 is a malicious package in bnpl-blocks-atom-bnpl-feedback, published on 5 Aug 2026. 

### Official description

On require('bnpl-blocks-atom-bnpl-feedback'), index.js loads _bridge.js which selects a platform-specific asset, downloads an unsigned binary via HTTPS from string-split-obfuscated Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev, cf101-adf, cf102-baf, cf103-070.workers.dev) with a base64-over-DNS-TXT covert-channel fallback resolving under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru, writes it to /tmp or %TEMP% under disguised names (.cache_<rnd> on Unix, dotnet_diag_<rnd>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh or cmd. The package's stated purpose is a 'data mapper' and index.js exports a trivial no-op class with no dependencies, contradicting the network-dropper behavior implemented in _bridge.js. Hostnames are reconstructed at runtime from split string arrays joined with empty separators to evade static matching.

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

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

## Sources

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

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