What does the dolyame-boxy-fonts malware do?

On require() of dolyame-boxy-fonts, index.js unconditionally loads./_loader.js, which reconstructs C2 hostnames from split-string arrays (Cloudflare Workers subdomains oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) and a DNS-TXT fallback channel under *.dl.wel1.ru (chunk-count via c. , base64 chunks via N. retrieved through dns.resolveTxt). _loader.js downloads a platform-specific binary, writes it to /tmp or %TEMP% under a hidden/decoy name (.cache_ or dotnet_diag_ .exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. The fetched bytes are opaque, unpinned, and not hash-verified, and the desti

Which versions of dolyame-boxy-fonts are malicious?

The following npm versions of dolyame-boxy-fonts are flagged malicious: 35.4.8. Treat any of these as compromised.

How do I remediate dolyame-boxy-fonts if I installed it?

dolyame-boxy-fonts establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed dolyame-boxy-fonts — how do I know if it already compromised me?

If dolyame-boxy-fonts was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dolyame-boxy-fonts part of a known attack campaign?

Yes — dolyame-boxy-fonts is associated with the IN-MAL-2026-015682, GHSA-rphf-wm4q-p6rj campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dolyame-boxy-fonts across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dolyame-boxy-fonts (version 35.4.8).

Malicious package

dolyame-boxy-fontsnpm

Advisory published Aug 5, 2026Updated Aug 6, 2026

dolyame-boxy-fonts is a confirmed malicious npm package (MAL-2026-13311) that opens a backdoor for remote access (malicious version 35.4.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-boxy-fonts (npm)

MAL-2026-13311

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dolyame-boxy-fonts

What this malware does

On require() of dolyame-boxy-fonts, index.js unconditionally loads./loader.js, which reconstructs C2 hostnames from split-string arrays (Cloudflare Workers subdomains oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) and a DNS-TXT fallback channel under *.dl.wel1.ru (chunk-count via c.<domain>, base64 chunks via N.<domain> retrieved through dns.resolveTxt). loader.js downloads a platform-specific binary, writes it to /tmp or %TEMP% under a hidden/decoy name (.cache<rand> or dotnet_diag<rand>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. The fetched bytes are opaque, unpinned, and not hash-verified, and the destination hosts are anonymous Cloudflare Workers subdomains assembled at runtime to defeat static grep. A sibling module lib/telemetry.js ships in the tarball with the same dropper primitives (require('child_' + 'process') string-split, fs['chmod' + 'Sync'], cp.spawn('/bin/sh', ['-c', filePath + ' &'])), providing an alternate execution path. Installing or requiring this package causes attacker-controlled code to execute on the installer's machine.

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.

Malicious versions

1 flagged

35.4.8

Indicators of compromise (SHA-256)

00cfc61444739291be87199c8b4118dd762690f12041bdadcd6b5792b4a3c9c3

8fc78c53700a2acd4b24e0604a5f8b99e8e425b04b17a32aae2ed79ae8422be9

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for dolyame-boxy-fonts (version 35.4.8).
If you installed it — respond
dolyame-boxy-fonts establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If dolyame-boxy-fonts was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dolyame-boxy-fonts on npm has been identified as a malicious package (version 35.4.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015682GHSA-rphf-wm4q-p6rj

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-boxy-fonts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database