Malicious code in ded-pwa-c-boxy (npm)
The npm package ded-pwa-c-boxy contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure upon require(). The package masqueraded as a UI component library but contained a sophisticated loader that reconstructed C2 hostnames, fetched opaque binaries, and spawned them as detached processes.
- Disclosed
- Last updated
- Blast radius
- Any npm consumer of ded-pwa-c-boxy package
- Ecosystems
- Attack vectors
- Affected entities
- ded-pwa-c-boxynpm package containing malicious loader code
The npm package ded-pwa-c-boxy was found to contain malicious code in its index.js entry point. Upon require(), the package loads _vendor.js, which reconstructs command-and-control hostnames from split-string arrays pointing to oob-worker.cf102-baf.workers.dev and sdk.dl.wel1.ru, with a DNS-TXT covert-channel fallback mechanism.
The malicious loader fetches a platform-specific opaque binary over HTTPS and writes it to temporary directories (/var/tmp on Unix or %TEMP% on Windows) under names disguised as system caches (.cache_ or dotnet_diag_.exe). The binary is then made executable (chmod 0755) and spawned as a detached process via /bin/sh -c on Unix or cmd.exe /c start /b on Windows.
The loader is wrapped in a try/catch block that silently swallows all errors and is gated on environment variables (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and a filesystem TTL marker to evade repeated analysis. The package.json declares the package as 'Reusable ded pwa c boxy components' with no dependencies, and index.js exposes only a trivial DedPwaCBoxy class—the declared purpose bears no relation to native-binary execution.
The C2 infrastructure uses anonymous Cloudflare Workers subdomains and lookalike DNS namespaces rather than publisher-owned or documented distribution hosts, indicating intentional obfuscation.
Indicators of compromise
- Packages
- ded-pwa-c-boxy
- Domains
- oob-worker.cf102-baf.workers.dev
- sdk.dl.wel1.ru
Remediation
- Immediately remove ded-pwa-c-boxy from all projects and dependencies
- Audit npm install logs and package-lock.json for any installation of ded-pwa-c-boxy
- Scan systems that installed this package for unexpected binaries in /var/tmp, %TEMP%, or system cache directories
- Review process execution logs for spawned processes from /bin/sh or cmd.exe with suspicious arguments
- Check for outbound HTTPS connections to oob-worker.cf102-baf.workers.dev or sdk.dl.wel1.ru
- Regenerate any credentials or secrets that may have been exposed on affected systems
- Monitor for DNS queries to wel1.ru or related lookalike domains
Sources
- GitHub Advisory GHSA-vqcq-x8r4-gh52 · GitHub Advisory Database
Cite this entry
"Malicious code in ded-pwa-c-boxy (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-ded-pwa-c-boxy-npm-1k4n4b
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in github-policy-bot (npm)
The npm package github-policy-bot contained malicious code that exfiltrated host identifiers and environment metadata during installation via a postinstall script. The package name shadowed a legitimate Google-owned repository and was authored under a placeholder account claiming security research purposes.
npmCompromised packageTyposquatting - containedcritical
Malicious code in crypto-javas (npm)
The npm package crypto-javas contains malicious code in its postinstall hook and main entrypoint that harvests environment variables (including CI secrets like AWS_*, GITHUB_TOKEN, NPM_TOKEN) and exfiltrates them to an attacker-controlled backend. The package is presented deceptively as @wizlabs/js-crypto with a placeholder repository.
npmCompromised packageTyposquatting - containedcritical
Malicious code in flydev (npm)
The npm package flydev contains malicious code designed to destroy Windows systems. The package masquerades as a utility but executes destructive operations including filesystem deletion, process termination, memory exhaustion, and fork bombs when invoked.
npmCompromised package - containedcritical
Malicious code in npm-wold (npm)
npm-wold@1.1.1 contains malicious code in its postinstall script that fetches remote JSON from a hardcoded endpoint and dynamically invokes attacker-controlled functions with attacker-supplied arguments, enabling code execution at install time.
npmCompromised package