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


- **Type:** Malicious package
- **Package:** `dolyame-boxy-mobile-bnpl-picture-gallery` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-13126?

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

### Official description

On require of this package, index.js unconditionally loads _ext.js, which reconstructs C2 hostnames at runtime by joining split string fragments (assembling *.workers.dev endpoints with a DNS TXT-record fallback resolving under *.dl.wel1.ru). _ext.js selects a platform-specific URL, downloads an opaque native binary via https.get, writes it to a hidden temp file named.cache_<hex> on Unix or dotnet_diag_<hex>.exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c '<path> &' or cmd /c start. Function references such as child_process are string-concatenated (require("child_"+"process")) and file names masquerade as.NET diagnostic or cache artifacts; comments frame the behavior as opt-out telemetry. A secondary dropper with matching primitives (base64 chunk assembly, fs.chmodSync|0o755, cp.spawn('/bin/sh', ['-c', path+' &'])) is shipped as lib/telemetry.js (~81KB), not referenced from index.js in this version but bundled in the tarball. The package name impersonates a payments/BNPL gallery SDK; the actual runtime behavior is a drop-and-execute of author-controlled native code on any host that installs or imports this version.

## What should I do about MAL-2026-13126?

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

## Sources

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

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