boxy-wrapper-rspack-pluginnpm
boxy-wrapper-rspack-plugin is a confirmed malicious npm package (MAL-2026-13098) that executes malicious code on install (malicious version 35.8.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in boxy-wrapper-rspack-plugin (npm)
What this malware does
The package advertises itself as an rspack plugin but ships a stub index.js that silently require()s adapter.js, which runs at module load time. adapter.js constructs Cloudflare Workers hostnames via string-array joins (e.g. 'oob-worker.cf100-416.workers.dev', 'oob-worker.cf101-adf.workers.dev', 'oob-worker.cf99-9b3.workers.dev', 'oob-worker.cf102-baf.workers.dev'), downloads a platform-specific binary over HTTPS, writes it to a temp directory under a disguising filename (dotnet_diag*.exe /.cache*), chmods it 0o755, and spawns it detached via child_process. If the HTTPS fetch fails, loadViaDns() queries TXT records under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, base64-reassembles the chunked TXT payload into an executable buffer, and executes it the same way. Environment flags such as DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK and a /tmp/.analytics_state cache file provide a telemetry-style cover story. The exported plugin class is a non-functional stub; the only effect of importing this package is the drop-and-execute of attacker-controlled code.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for boxy-wrapper-rspack-plugin (version 35.8.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-wrapper-rspack-plugin across your stack and pipelines.
If you installed it — respond
Remove boxy-wrapper-rspack-plugin 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-wrapper-rspack-plugin 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-wrapper-rspack-plugin 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks boxy-wrapper-rspack-plugin-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.