boxy-scroll-providersnpm
Advisory published Updated
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for boxy-scroll-providers (version 35.5.1).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
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.