boxy-pkg-deps-hashnpm
boxy-pkg-deps-hash is a confirmed malicious npm package (MAL-2026-13075) that executes malicious code on install (malicious version 35.1.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in boxy-pkg-deps-hash (npm)
What this malware does
On require() of the package, index.js loads adapter.js and unconditionally invokes setup(). setup() downloads a platform-specific binary from hardcoded Cloudflare Workers hosts whose names are assembled at runtime via array-join to defeat string search (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev). The fetched bytes are written to /tmp or %TEMP% under disguised filenames (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. If HTTPS retrieval fails, _adapter.js falls back to a DNS-TXT covert channel: it resolves TXT records under c.<subdomain>.dl.wel1.ru to get a chunk count, then TXT records under N.<subdomain>.dl.wel1.ru to reconstruct base64 chunks, concatenates and decodes them to the same binary, and executes it via the same write/chmod/spawn path. The destination hosts are anonymous *.workers.dev endpoints unrelated to any declared publisher, and env checks use benign-sounding cover names (DISABLE_TELEMETRY/DO_NOT_TRACK). Any import of the package results in full-host remote code execution on the installer.
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-pkg-deps-hash (version 35.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging boxy-pkg-deps-hash across your stack and pipelines.
If you installed it — respond
Remove boxy-pkg-deps-hash 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-pkg-deps-hash 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-pkg-deps-hash 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-pkg-deps-hash-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.