# MAL-2026-13307: Malicious code in dolyame-boxy-desktop-bnpl-picture-gallery (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-desktop-bnpl-picture-gallery` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-gf73-fvqq-2f8f

## What is MAL-2026-13307?

MAL-2026-13307 is a malicious package in dolyame-boxy-desktop-bnpl-picture-gallery, published on 5 Aug 2026. 

### Official description

On require of this package, index.js loads _bridge.js which auto-executes an init routine that fetches a platform-specific binary from runtime-assembled Cloudflare Workers hosts (assembled from split fragments joined with.join('') to hide the destination, resolving to oob-worker.cf10x-*.workers.dev). The binary is written under /var/tmp or %TEMP% with disguised names such as dotnet_diag_<rand>.exe or.cache_<rand>, chmod 0755, and spawned detached via /bin/sh -c or cmd.exe. A DNS-TXT fallback channel under *.dl.wel1.ru (resolver domains also assembled from split fragments) reads a count from c.<domain> TXT and iterates <n>.<domain> TXT records, base64-decoding the concatenation into an alternate payload delivery resilient to HTTP egress filtering. Destination hosts and resolver domains are obfuscated via string-split concatenation.

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

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

## Sources

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

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