dolyame-boxy-atom-icon-loader (npm) · Malicious Code
Affects dolyame-boxy-atom-icon-loaderSource GCVE Database
Malicious package : remove dolyame-boxy-atom-icon-loader and rotate any secrets on hosts that installed it.
Data as of 6 Aug 2026, 18:24 UTC
Malicious package
Published to npm · OSV MAL-2026-13297
What to do
Remove dolyame-boxy-atom-icon-loader from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmdolyame-boxy-atom-icon-loader | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (34c580f021e76e3cff3c4a92cac6c53ef918c49db3c1d0b8eae008dd51dca766) 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. ## Source: ghsa-malware (03baa2c099e2df5b44af4bdd58c79ed8cb97069284035967f7de9efaf1e30df1) 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.