# MAL-2026-12365: Malicious code in dolyame-boxy-independent-bnpl-info-images (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-independent-bnpl-info-images` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-r7x5-x2pm-qx2v

## What is MAL-2026-12365?

MAL-2026-12365 is a malicious package in dolyame-boxy-independent-bnpl-info-images, published on 5 Aug 2026. 

### Official description

On require() of the package, index.js loads _adapter.js which selects a platform-specific payload path, downloads a binary from runtime-assembled Cloudflare workers.dev hostnames (with a DNS TXT fallback channel via *.dl.well1.site), writes it to /var/tmp or %TEMP% under decoy names (.cache_<hex>, dotnet_diag_<hex>.exe,.analytics_state), chmods it 0755, and spawns it detached via /bin/sh -c or cmd. Destination hostnames are assembled by Array.join from split fragments to evade static matching. The package's advertised public API (DolyameBoxyIndependentBnplInfoImages with init/version/configure) is a no-op wrapper; the only real behavior triggered by importing the package is the covert binary drop-and-execute in _adapter.js. No hash or signature verification is performed on the fetched binary, and the destination hosts are unrelated to any BNPL/imaging functionality the name implies.

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

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-12365 is a malicious package: dolyame-boxy-independent-bnpl-info-images (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-12365/ (Markdown: https://insights.sbomify.com/MAL-2026-12365/index.md)
```

## Sources

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

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