# MAL-2026-13327: Malicious code in dolyame-boxy-independent-bnpl-scheme (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-independent-bnpl-scheme` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-4c3q-jjpc-xjwp

## What is MAL-2026-13327?

MAL-2026-13327 is a malicious package in dolyame-boxy-independent-bnpl-scheme, published on 5 Aug 2026. 

### Official description

On require of this package, index.js loads setup.js which downloads a platform-specific native binary from author-controlled Cloudflare Workers hosts (with a DNS TXT fallback via sdk.dl.wel1.ru), writes it to /var/tmp or %TEMP% under disguised filenames (.cache_<hex>, dotnet_diag_<hex>.exe), chmods it to 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Destination hostnames are reconstructed from array-joined string fragments (e.g. ['oob-worker','.cf10','1-adf.w','ork','ers.d','ev'].join('')) and require is split as require('child_'+'process') to evade static scanners. Execution is gated by a lockfile cooldown to run once per host. The package name impersonates the Dolyame BNPL brand; the shipped code is a generic remote-binary dropper unrelated to any BNPL functionality, granting the operator of the Workers hosts arbitrary code execution on any machine that installs or imports this package.

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

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

## Sources

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

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