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

ded-pwa-c-page-maker-propsnpm

ded-pwa-c-page-maker-props is a confirmed malicious npm package (MAL-2026-13497) that executes malicious code on install (malicious version 35.7.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ded-pwa-c-page-maker-props (npm)

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

What this malware does

On require of the package, compat.js selects a platform-specific endpoint and fetches an opaque binary from string-obfuscated Cloudflare Workers hosts (oob-worker.cf101/cf102/cf103-*.workers.dev, cf99-9b3.workers.dev), writes it to /tmp/.cache<rand> on POSIX or %TEMP%\dotnet_diag_<rand>.exe on Windows, chmods 0755, and spawns it detached via /bin/sh or cmd.exe. Destination hostnames and dropped filenames are assembled from split string arrays joined at runtime, and checks against DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK are used as a cover story to gate the drop. If the HTTPS fetch fails, the code falls back to a DNS-TXT covert channel: it queries c.<domain> under *.dl.wel1.ru for a chunk count and reassembles a base64 binary payload from sequential TXT records at sdk/ext/pkg/net.dl.wel1.ru. The package advertises itself as a PWA props module but ships no such functionality; the sole install/import-time effect is fetching and executing an unsigned attacker binary on the installer's machine.

Malicious versions

1 flagged
35.7.7

Indicators of compromise (SHA-256)

4e3ee97f7402c39b73312351f193309dd6cd6e21704c8ee384e8e74e76cca0da

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-c-page-maker-props (version 35.7.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-pwa-c-page-maker-props across your stack and pipelines.

  2. If you installed it — respond

    Remove ded-pwa-c-page-maker-props 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-c-page-maker-props 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-c-page-maker-props 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-c-page-maker-props on npm has been identified as a malicious package (version 35.7.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016877

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ded-pwa-c-page-maker-props-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.

Explore

ded-pwa-c-page-maker-props (npm) malicious package — MAL-2026-13497 | O3 Security