Which versions of dolyame-boxy-stories-of-block are malicious?

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

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

dolyame-boxy-stories-of-block is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-boxy-stories-of-block, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed dolyame-boxy-stories-of-block — how do I know if it already compromised me?

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

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

Malicious package

dolyame-boxy-stories-of-blocknpm

dolyame-boxy-stories-of-block is a confirmed malicious npm package (MAL-2026-13132) that typosquats a legitimate package to trick installs (malicious version 35.8.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-boxy-stories-of-block (npm)

MAL-2026-13132

Immediate action

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

npm uninstall dolyame-boxy-stories-of-block

What this malware does

On require() of the package's main entry, index.js unconditionally loads support.js, which reconstructs hostnames from split-string arrays (e.g. ['oob-worker.cf99-9b3.worker','s.dev'].join('') and ['sdk.dl.wel','1.ru'].join('')), fetches a platform-specific binary over HTTPS from Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev) and *.dl.wel1.ru endpoints with a DNS-TXT chunked fallback, writes it to /tmp/.cache<rnd> on Unix or %TEMP%\dotnet_diag_<rnd>.exe on Windows, chmods it 0755, and spawns it detached via cp.spawn('/bin/sh',['-c', fp+' &'],{detached:true}).unref() or cmd /c start. No hash or signature verification is performed despite a comment claiming SHA-256 integrity. The dropped filename and marker file (.analytics_state) mimic system artifacts, and DISABLE_TELEMETRY / DO_NOT_TRACK env-var checks provide a benign 'analytics SDK' cover story. A second dropper module at lib/telemetry.js (~81KB) implements the same fetch/chmod/spawn shape with base64-decoded payload chunks and endpoint rotation.

Malicious versions

1 flagged

35.8.6

Indicators of compromise (SHA-256)

1e18c95ca0abb6765cd4e9eb0ac8661962453f51c14d55902402a3b861d8ff16

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-boxy-stories-of-block (version 35.8.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-stories-of-block across your stack and pipelines.
If you installed it — respond
dolyame-boxy-stories-of-block is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-boxy-stories-of-block, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If dolyame-boxy-stories-of-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-stories-of-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-stories-of-block on npm has been identified as a malicious package (version 35.8.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015642

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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