Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

ded-pwa-ded-pwa-corenpm

ded-pwa-ded-pwa-core is a confirmed malicious npm package (MAL-2026-13498) that executes malicious code on install (malicious version 35.6.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ded-pwa-ded-pwa-core (npm)

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

What this malware does

On require('ded-pwa-ded-pwa-core'), index.js unconditionally loads adapter.js, which selects a platform-specific target path (%TEMP%/dotnet_diag<hex>.exe on Windows, /tmp/.cache_<hex> on POSIX), fetches an opaque binary over HTTPS from author-controlled Cloudflare Workers endpoints, writes it to disk, chmods 0755, and detached-spawns it via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}) or cmd. The destination hostnames are reconstructed at runtime from split-string arrays (e.g. ['oob-worker.cf100-416.workers.','dev'].join('') and ['sdk.','dl','.wel1','.r','u'].join('') yielding sdk.dl.wel1.ru) to evade static grepping, and identifier lookups such as require('child_'+'process') and fs['chmod'+'Sync'] are similarly split. A DNS-TXT chunked-base64 fallback via *.dl.wel1.ru is present. Staged filenames masquerade as.NET diagnostics tooling or hidden cache files, and DO_NOT_TRACK / ANALYTICS_OPT_OUT env checks provide a telemetry cover story despite the executed content being an opaque author-controlled binary with no version pinning and no hash verification. Installing or requiring the package results in arbitrary code execution on the installer's host.

Malicious versions

1 flagged
35.6.3

Indicators of compromise (SHA-256)

97666216930384a372fdf45c3c6a5d744e61de4b8e5c01f82a6ffe5688b168e7

Detection & response playbook

Malicious package

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ded-pwa-ded-pwa-core (version 35.6.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-pwa-ded-pwa-core across your stack and pipelines.

  2. If you installed it — respond

    Remove ded-pwa-ded-pwa-core 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.

  3. Did it already run?

    If ded-pwa-ded-pwa-core 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.

  4. How O3 protects you

    O3 blocks ded-pwa-ded-pwa-core 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

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

Campaign

IN-MAL-2026-016896

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ded-pwa-ded-pwa-core-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.

Malware detection Runtime egress monitoring

Explore

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