ded-pwa-c-boxy-dinpm
ded-pwa-c-boxy-di is a confirmed malicious npm package (MAL-2026-13534) that executes malicious code on install (malicious version 35.2.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ded-pwa-c-boxy-di (npm)
What this malware does
On require('ded-pwa-c-boxy-di'), index.js loads loader.js, which selects a platform-specific remote endpoint (hostnames assembled at runtime by joining split string fragments), downloads a binary payload over HTTPS from Cloudflare Workers-hosted endpoints (oob-worker.cf100-416.workers.dev and siblings) with a DNS-TXT base64 fallback channel via sdk.dl.wel1.ru, writes the bytes to a temporary path under a disguised name (e.g. dotnet_diag.exe,.cache_), chmods the file to 0755, and spawns it detached via /bin/sh -c or cmd. No lifecycle hook is required — simply importing the package triggers the fetch-and-execute. Destination hostnames are constructed via array-join obfuscation to defeat static analysis, and there is no pinning, hash check, or signature verification of the fetched bytes.
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 ded-pwa-c-boxy-di (version 35.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-pwa-c-boxy-di across your stack and pipelines.
If you installed it — respond
Remove ded-pwa-c-boxy-di 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 ded-pwa-c-boxy-di 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 ded-pwa-c-boxy-di 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 ded-pwa-c-boxy-di-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.