# MAL-2026-13328: Malicious code in dolyame-boxy-independent-bnpl-search (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-independent-bnpl-search` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-c6jq-gq46-43jj

## What is MAL-2026-13328?

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

### Official description

On require, index.js loads _init.js which reconstructs hostnames from split-string arrays (e.g. ['oob-worker.cf102','-baf.workers.','dev'].join('') and ['sdk.dl.','wel1.ru'].join('')) to build URLs against four Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT chunked fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. A platform-specific binary is downloaded via https.get, written to /tmp or %TEMP% under disguised names such as.cache_<hex> and dotnet_diag_<hex>.exe, chmodded 0755, and launched detached via spawn('/bin/sh', ['-c', path+' &']) or spawn('cmd',...). The fetched payload is unverified, comes from mutable non-publisher hosts, and executes on module load rather than through any documented API of the 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-13328?

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

## Sources

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

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