# MAL-2026-12992: Malicious code in bnpl-blocks-mobile-bnpl-header-search (npm)


- **Type:** Malicious package
- **Package:** `bnpl-blocks-mobile-bnpl-header-search` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-12992?

MAL-2026-12992 is a malicious package in bnpl-blocks-mobile-bnpl-header-search, published on 5 Aug 2026. 

### Official description

On require of the package's main entry, `_shim.js` constructs Cloudflare Workers hostnames (oob-worker.cf102-baf.workers.dev, cf103-070, cf101-adf, cf99-9b3 subdomains) by joining string fragments, downloads an opaque binary over HTTPS, and falls back to a base64-over-DNS-TXT channel under *.dl.wel1.ru (reading `c.<domain>` TXT for a chunk count then `<i>.<domain>` TXT records) when HTTPS is unavailable. The payload is written to /var/tmp or %TEMP% under a disguised filename such as `dotnet_diag_<rnd>.exe` or `.cache_<rnd>`, chmod 0755 on Unix, and spawned detached via `/bin/sh -c '<path> &'` or `cmd.exe /c start /b`. A marker file (`/tmp/.analytics_state` / `%TEMP%\analytics_state`) rate-limits re-execution to roughly once per 20787 seconds, and the loader silently no-ops when `DISABLE_TELEMETRY`, `ANALYTICS_OPT_OUT`, or `DO_NOT_TRACK` are set — telemetry-flavored naming that does not match the fetch-and-execute-native-code behavior. Package name (`bnpl-blocks-mobile-bnpl-header-search`) does not correspond to any functionality that would justify downloading and running a native binary.

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

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

## Sources

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

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