Which versions of dolyame-boxy-block are malicious?

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

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

Remove dolyame-boxy-block 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-block — how do I know if it already compromised me?

If dolyame-boxy-block 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-block part of a known attack campaign?

Yes — dolyame-boxy-block is associated with the IN-MAL-2026-015700 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-block 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-block (version 35.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-block across your stack and pipelines.

Malicious package

dolyame-boxy-blocknpm

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

Malicious code in dolyame-boxy-block (npm)

MAL-2026-13298

Immediate action

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

npm uninstall dolyame-boxy-block

What this malware does

[email protected] ships a _runtime.js module that is unconditionally required from index.js at load time. On import, _runtime.js reconstructs attacker-controlled hostnames from split string arrays (e.g. ["oob-wor","ker.cf99-9b3.workers.dev"].join("") producing oob-worker.cf99-9b3.workers.dev, and similar for oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev), performs an https.get to a platform-specific endpoint, writes the returned bytes to /var/tmp or %TEMP% under a decoy filename (.cache_<rand> on POSIX, dotnet_diag_<rand>.exe on Windows), chmod 0755s the file, and spawns it detached via /bin/sh -c "<path> &" or cmd.exe with stdio:"ignore" and .unref(). If the HTTPS mirrors fail, a DNS-TXT covert channel under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru retrieves a base64-encoded payload chunked across multiple TXT records (c.<domain>, 0.<domain>, 1.<domain>...), reassembles it, and executes it through the same write-and-spawn sink. The advertised purpose ("boxy block" UI library) does not match the shipped behavior; the hostnames are obfuscated to evade static string search; the fetched binary is unpinned, unhashed, and unsigned. Any consumer that require()s or imports the package triggers full-host remote code execution.

Malicious versions

1 flagged

35.5.2

Indicators of compromise (SHA-256)

919c54c4e8e0b08b62f76b85369a9033929f8ea19dfc777b8ece48697229a5ce

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-block (version 35.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-block across your stack and pipelines.
If you installed it — respond
Remove dolyame-boxy-block 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-block 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-block 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-block on npm has been identified as a malicious package (version 35.5.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015700

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-boxy-block-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