# MAL-2026-13293: Malicious code in dolyame-boxy-atom-desktop-bnpl-container (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-atom-desktop-bnpl-container` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-j64m-4266-c3cv

## What is MAL-2026-13293?

MAL-2026-13293 is a malicious package in dolyame-boxy-atom-desktop-bnpl-container, published on 5 Aug 2026. 

### Official description

On require(), index.js loads _bootstrap.js, which reconstructs remote hosts by array.join string concatenation (oob-worker.cf100-416.workers.dev, cf101-adf.workers.dev, cf103-070.workers.dev, with a *.dl.wel1.ru DNS-TXT fallback), downloads an opaque platform-specific binary over HTTPS (or via chunked base64 in DNS TXT records against c.<domain>/i.<domain> when HTTPS is unavailable), writes it to /var/tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods 0755, and spawns it detached and unref'd with stdio ignored via /bin/sh -c or cmd /c start. The package presents itself as a trivial BNPL container wrapper and ships no code related to that stated purpose; the fetched bytes are neither pinned nor hash-verified, the destinations are obfuscated to defeat static inspection, the DNS-TXT channel is designed to bypass HTTPS egress filtering, and the on-disk filenames impersonate legitimate diagnostic/cache artifacts.

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

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

## Sources

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

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