# MAL-2026-12929: Malicious code in bnpl-blocks-desktop-bnpl-image-with-caption (npm)


- **Type:** Malicious package
- **Package:** `bnpl-blocks-desktop-bnpl-image-with-caption` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-12929?

MAL-2026-12929 is a malicious package in bnpl-blocks-desktop-bnpl-image-with-caption, published on 5 Aug 2026. 

### Official description

On require of this package, index.js loads _ext.js which selects a platform-specific asset name and downloads a native binary from obfuscated Cloudflare Workers hostnames (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev), assembled at runtime by joining split string fragments. If HTTPS delivery fails, the code falls back to a DNS TXT-record channel under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, concatenating and base64-decoding chunked TXT responses into a binary payload. The payload is written to /tmp or %TEMP% under disguised names such as dotnet_diag_<tag>.exe and.cache_<tag>, chmodded 0755, and spawned detached via cp.spawn("/bin/sh", ["-c", fp+" &"], {detached:true}) or spawn("cmd",...). No hash or signature verification is performed. The 'child_process' module identifier is also reconstructed via string-splitting, and cover-story comments label the behavior as 'telemetry' and 'analytics' with a state file 'analytics_state'. The package's stated purpose (a reusable UI block) does not justify any binary fetch or execution.

## What should I do about MAL-2026-12929?

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

## Sources

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

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