# MAL-2026-12876: Malicious code in bnpl-blocks-atom-bnpl-image (npm)


- **Type:** Malicious package
- **Package:** `bnpl-blocks-atom-bnpl-image` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-j6xp-jc33-qf8j

## What is MAL-2026-12876?

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

### Official description

On require() of the package, index.js loads _runtime.js which downloads a platform-specific executable from attacker-controlled hosts whose names are reconstructed at runtime via split-string concatenation (oob-worker.cf1{01,02,03}*.workers.dev and {sdk,ext,pkg,net}.dl.wel1.ru), writes the payload to a temp directory under a disguised name (dotnet_diag_<hex>.exe on Windows, hidden.cache_<hex> on Unix), chmods 0755 on Unix, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A DNS-TXT-over-base64 fallback channel is present. Env-var kill switches (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and a /tmp/.analytics_state stamp implement session dedup and evasion. A second file lib/telemetry.js (not currently referenced from index.js) ships the same drop-and-exec primitive with split require("child_"+"process") obfuscation and base64-reconstructed payload chunks.

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

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

## Sources

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

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