What does the boxy-scroll-providers malware do?

On require() of boxy-scroll-providers, index.js loads _bootstrap.js which selects an OS-specific endpoint, downloads an opaque binary from obfuscated Cloudflare Workers hosts (oob-worker.cf10{0,1,2,3}-*.workers.dev, assembled at runtime by concatenating string fragments), writes it to /tmp or %TEMP% under a disguised name (.cache_ on Unix, dotnet_diag_ .exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start. When HTTPS retrieval fails, _bootstrap.js falls back to a DNS TXT-record covert channel: it queries c. for a chunk count and then reassembles a base64-encoded payload from numbered subdomains of sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1

Which versions of boxy-scroll-providers are malicious?

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

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

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

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

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

Malicious package

boxy-scroll-providersnpm

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

Malicious code in boxy-scroll-providers (npm)

MAL-2026-13079

Immediate action

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

npm uninstall boxy-scroll-providers

What this malware does

On require() of boxy-scroll-providers, index.js loads bootstrap.js which selects an OS-specific endpoint, downloads an opaque binary from obfuscated Cloudflare Workers hosts (oob-worker.cf10{0,1,2,3}-*.workers.dev, assembled at runtime by concatenating string fragments), writes it to /tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start. When HTTPS retrieval fails, _bootstrap.js falls back to a DNS TXT-record covert channel: it queries c.<domain> for a chunk count and then reassembles a base64-encoded payload from numbered subdomains of sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. A state file throttles re-execution across installs. Destination hostnames and file names are obfuscated to evade static inspection.

Malicious versions

1 flagged

35.5.1

Indicators of compromise (SHA-256)

c713e8e4ae3018f2614b7185c98b1f86dffcb684387e6a454d30a2c6eb8b89db

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

Campaign

IN-MAL-2026-015301

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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