# MAL-2026-13326: Malicious code in dolyame-boxy-independent-bnpl-preset-container (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-independent-bnpl-preset-container` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-rr4c-36r7-8vp4

## What is MAL-2026-13326?

MAL-2026-13326 is a malicious package in dolyame-boxy-independent-bnpl-preset-container, published on 5 Aug 2026. 

### Official description

index.js require()s _platform.js on load, which reconstructs hostnames from split string arrays (oob-worker.cf10*-*.workers.dev and sdk.dl.wel1.ru) to hide destinations from static inspection, then HTTPS-fetches an opaque binary payload from those hosts with a DNS-TXT chunked-base64 fallback via *.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under a randomized hidden filename (.cache_<rand> / dotnet_diag_<rand>.exe), chmod 0755, then spawned detached via /bin/sh -c or cmd.exe (_platform.js line 119-125). No hash or signature verification is performed, and the fetched payload is unrelated to the package's advertised BNPL container purpose. A.analytics_state marker file and DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK opt-out flags provide cover-story framing over the loader. The dropper fires at module require time.

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

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

## Sources

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

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