Which versions of dolyame-boxy-scroll are malicious?

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

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

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

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

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

Malicious package

dolyame-boxy-scrollnpm

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

Malicious code in dolyame-boxy-scroll (npm)

MAL-2026-13130

Immediate action

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

npm uninstall dolyame-boxy-scroll

What this malware does

On require('dolyame-boxy-scroll'), index.js loads ext.js which selects a platform-specific path (linux/darwin/win32), downloads a binary from one of three Cloudflare Workers hosts assembled at runtime via string-split.join() (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev), writes it to /var/tmp or %TEMP% under a disguised name (.cache<rand>, dotnet_diag_<rand>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b (_ext.js line 122-128). A DNS-TXT fallback channel reconstructs a base64 payload from concatenated TXT records at sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru when the HTTPS fetch fails. The fetched bytes are not pinned, hashed, or signature-verified. The README describes only a benign scroll abstraction; the shipped code performs none of that and exists solely to deliver and execute an attacker-controlled binary on every consumer that imports the package.

Malicious versions

1 flagged

35.9.9

Indicators of compromise (SHA-256)

32273cf2b594fbdf7b09058c383c7d40319001732490771eda7931aaf01bf451

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

Campaign

IN-MAL-2026-015648

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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