ded-pwa-c-cmsnpm
ded-pwa-c-cms is a confirmed malicious npm package (MAL-2026-13496) that opens a backdoor for remote access (malicious version 35.9.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ded-pwa-c-cms (npm)
What this malware does
On require('ded-pwa-c-cms'), index.js loads platform.js which selects a platform-specific URL path and downloads an opaque binary over HTTPS from obfuscated author-controlled hosts (Cloudflare Workers subdomains such as oob-worker.cf*-*.workers.dev and *.dl.wel1.ru subdomains including sdk/ext/pkg/net), with a DNS-TXT chunked base64 fallback channel (count read from c.<domain>, chunks read from i.<domain>). The fetched bytes are written to /tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}).unref() (or the cmd equivalent). C2 hostnames are reassembled at runtime from split-string arrays joined with.join(''), and execution is gated behind DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env checks as a telemetry cover story. The package advertises itself as a pluggable CMS interface with no dependencies and no legitimate need for a native binary; the dotnet_diag filename masquerades as a Microsoft diagnostic tool. No hash/signature verification is performed on the fetched payload.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ded-pwa-c-cms (version 35.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-pwa-c-cms across your stack and pipelines.
If you installed it — respond
ded-pwa-c-cms establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ded-pwa-c-cms 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-cms 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-cms-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.