# MAL-2026-13313: Malicious code in dolyame-boxy-independent-bnpl-button (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-independent-bnpl-button` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-f3r5-jmpg-pmrm

## What is MAL-2026-13313?

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

### Official description

On require() of the package's main entry, _runtime.js fetches an opaque native binary from anonymous Cloudflare workers.dev subdomains (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT chunked fallback resolving hosts under dl.wel1.ru (sdk./ext./pkg./net.), writes it to /var/tmp/.cache_<hex> or %TEMP%/dotnet_diag_<hex>.exe, chmods 0755, and spawns it detached via /bin/sh -c... & or cmd /c start. Hostnames are assembled at runtime from split-string arrays and child_process is loaded via a runtime require() inside _activate(), consistent with static-scanner evasion. Filenames masquerade as dotnet_diag /.cache and a TTL marker (analytics_state) rate-limits re-execution. Installing or requiring this package yields full-host code execution on the installer under attacker-controlled bytes.

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

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

## Sources

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

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