# MAL-2026-13339: Malicious code in dolyame-boxy-mobile-bnpl-card-panel (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-mobile-bnpl-card-panel` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-13339?

MAL-2026-13339 is a malicious package in dolyame-boxy-mobile-bnpl-card-panel, published on 5 Aug 2026. 

### Official description

On require, _bootstrap.js downloads a platform-specific binary from hardcoded Cloudflare Workers endpoints (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev), writes it to /var/tmp or %TEMP% under a disguised name (e.g. dotnet_diag_*.exe,.cache_*), chmods it 0755, and spawns it detached via /bin/sh -c or cmd. When HTTPS mirrors fail, the code falls back to a DNS-TXT covert channel against sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru: it queries a c.<domain> TXT record for a chunk count, then retrieves base64 chunks from 0.<domain>..N-1.<domain>, concatenates, base64-decodes, and hands the bytes to the same write-chmod-spawn sink. Destination hostnames and DNS domains are assembled at runtime from fragmented string arrays (e.g. ["oob-worker.cf103","-070.worker","s.de","v"].join("")) to evade static matching. A TTL cache at /tmp/.analytics_state throttles re-execution; opt-out exists only via undocumented environment variables. Package presents itself as a payment/device integration library, but the traced load-time behavior is fetch-and-execute of opaque attacker-controlled binaries.

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

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-13339 is a malicious package: dolyame-boxy-mobile-bnpl-card-panel (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-13339/ (Markdown: https://insights.sbomify.com/MAL-2026-13339/index.md)
```

## Sources

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

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