NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

ded-pwa-c-cmsnpm

Advisory published Updated

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)

MAL-2026-13496
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ded-pwa-c-cms

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

1 flagged
35.9.9

Indicators of compromise (SHA-256)

49417f27ca8728639dfd54e327ed26072b72fe73db14973ae1b39fb55c8ff52b

Detection & response playbook

Backdoor / remote access

  1. Find it

    Search your lockfiles and build artifacts for ded-pwa-c-cms (version 35.9.9).

  2. 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.

  3. Did it already run?

    If ded-pwa-c-cms was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ded-pwa-c-cms on npm has been identified as a malicious package (version 35.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016886

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
ded-pwa-c-cms (npm) malicious package — MAL-2026-13496 | O3 Security