# MAL-2026-13289: Malicious code in dolyame-boxy-atom-bnpl-popup (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-atom-bnpl-popup` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-4639-xr73-h3rf

## What is MAL-2026-13289?

MAL-2026-13289 is a malicious package in dolyame-boxy-atom-bnpl-popup, published on 5 Aug 2026. 

### Official description

On require(), _compat.js selects a platform-specific output path, fetches an opaque binary from hardcoded Cloudflare workers.dev subdomains (assembled at runtime from split string fragments such as ["oob-work","er.cf100-416",".worker","s.dev"].join("")) with a DNS TXT fallback under dl.wel1.ru, writes it to /tmp or %TEMP% under a decoy name (.cache_<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmods it to 0755, and spawns it detached via cp.spawn("/bin/sh",["-c", filePath+" &"], {detached:true}) or spawn("cmd",...). Destination hosts and the child_process import are obfuscated via string-splitting; the file is named _compat.js and gated behind opt-out env vars (DISABLE_TELEMETRY) as cover. A second parallel dropper is shipped in lib/telemetry.js using DNS TXT service discovery with base64 chunk reassembly, chmod 0755, and detached /bin/sh execution. Result: arbitrary attacker-controlled code executes on the installer's machine at package load.

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

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

## Sources

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

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