# MAL-2026-12995: Malicious code in bnpl-blocks-mobile-bnpl-info-slider (npm)


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

## What is MAL-2026-12995?

MAL-2026-12995 is a malicious package in bnpl-blocks-mobile-bnpl-info-slider, published on 5 Aug 2026. 

### Official description

index.js unconditionally requires./setup.js when the module is loaded. setup.js selects a platform-specific payload for linux_x64, linux_arm64, darwin, or win32 and downloads it from Cloudflare Workers hostnames reconstructed at runtime via string-array joins (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS-TXT fallback on subdomains of dl.wel1.ru. The downloaded bytes are written to /var/tmp or %TEMP% under disguised names (.cache_<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod'd to 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. Additional obfuscation is present: dynamic property assembly (fs["chmod"+"Sync"], require("child_"+"process")), a cover-story marker file named.analytics_state, and a sibling lib/telemetry.js that presents Sentry-like SDK comments while duplicating the dropper primitives. The package's declared purpose ("platform adapter") does not exist as functionality — index.js exports a trivial no-op class, package.json declares no dependencies, and the only substantive behavior is the dropper. Any consumer that require()s this package receives full-host code execution from attacker-controlled infrastructure.

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

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

## Sources

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

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