Which versions of dolyame-boxy-markdown are malicious?

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

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

Remove dolyame-boxy-markdown from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If dolyame-boxy-markdown was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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

Yes — dolyame-boxy-markdown is associated with the IN-MAL-2026-015665 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-markdown across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-boxy-markdown (version 35.9.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-markdown across your stack and pipelines.

Malicious package

dolyame-boxy-markdownnpm

dolyame-boxy-markdown is a confirmed malicious npm package (MAL-2026-13336) that executes malicious code on install (malicious version 35.9.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-boxy-markdown (npm)

MAL-2026-13336

Immediate action

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

npm uninstall dolyame-boxy-markdown

What this malware does

On require() of dolyame-boxy-markdown, index.js loads ext.js which downloads a platform-specific native binary from author-controlled Cloudflare Workers subdomains (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS TXT covert-channel fallback under *.dl.wel1.ru (sdk/ext/pkg/net subdomains). The fetched bytes are written to /var/tmp or %TEMP% under disguised names (dotnet_diag<hex>.exe,.cache_<hex>), chmod 0755, then spawned detached via cmd.exe /c start /b on Windows or /bin/sh -c '<path> &' on Unix. No hash or signature verification is performed. Hostnames are constructed at runtime by joining split string fragments (e.g. ['oob-w','orker.cf101-adf.w','orkers.de','v'].join('')) to evade static scanners, and the disguised filenames plus 'telemetry'/'analytics' cover-story naming mask the dropper behavior. The package advertises itself as a markdown provider, a purpose with no legitimate need to fetch and execute native binaries from anonymous Cloudflare Workers hosts.

Malicious versions

1 flagged

35.9.4

Indicators of compromise (SHA-256)

373a9a2757b6b44dde0583e1cf35f5eabe8e360bf732e751630d8bb8ddb72ee6

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-boxy-markdown (version 35.9.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-markdown across your stack and pipelines.
If you installed it — respond
Remove dolyame-boxy-markdown from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dolyame-boxy-markdown was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks dolyame-boxy-markdown before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-015665

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-boxy-markdown-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database