# MAL-2026-13300: Malicious code in dolyame-boxy-desktop-bnpl-button-set (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-desktop-bnpl-button-set` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-hf9m-4wxq-3fcq

## What is MAL-2026-13300?

MAL-2026-13300 is a malicious package in dolyame-boxy-desktop-bnpl-button-set, published on 5 Aug 2026. 

### Official description

Requiring the package loads _vendor.js, which reconstructs remote hosts from array-join fragments (resolving to Cloudflare Workers hosts such as oob-worker.cf*.workers.dev and a *.dl.wel1.ru fallback discovered via DNS-TXT), downloads a platform-specific binary over HTTPS with no hash or signature verification, writes it to /tmp or %TEMP% under a disguised name (.cache_<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods it 0755, and spawns it detached via /bin/sh -c or cmd /c start. A TTL stamp is used to avoid re-fetching on subsequent loads. The advertised purpose (a BNPL button UI set) has no legitimate need for downloading and executing an external binary, and the destination hosts are obfuscated to defeat static string scanning.

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

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-13300 is a malicious package: dolyame-boxy-desktop-bnpl-button-set (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-13300/ (Markdown: https://insights.sbomify.com/MAL-2026-13300/index.md)
```

## Sources

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

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