# MAL-2026-13297: Malicious code in dolyame-boxy-atom-icon-loader (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-atom-icon-loader` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-5j2m-28q8-4955

## What is MAL-2026-13297?

MAL-2026-13297 is a malicious package in dolyame-boxy-atom-icon-loader, published on 5 Aug 2026. 

### Official description

Package advertised as an icon loader but on require() the bundled _vendor.js downloads a platform-specific executable from obfuscated Cloudflare workers.dev subdomains and *.dl.wel1.ru hosts (oob-worker.cf102-baf.workers.dev, sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), writes it to /var/tmp or %TEMP% under disguising names (dotnet_diag_*.exe,.cache_*), chmods it 0o755, and spawns it detached via /bin/sh or cmd. Destination hostnames and the child_process require target are reconstructed at runtime via array.join("") splits to evade static scanners. If HTTPS mirrors fail, _vendor.js falls back to a DNS-TXT covert channel that queries c.<domain> for chunk count then N.<domain> for base64-encoded chunks, reassembles the executable, and feeds it to the same write/chmod/exec sink. Behavior does not match the package's declared purpose.

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

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

## Sources

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

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