ded-pwa-c-micronpm
ded-pwa-c-micro is a confirmed malicious npm package (MAL-2026-13536) that executes malicious code on install (malicious version 35.8.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ded-pwa-c-micro (npm)
What this malware does
On require(), index.js loads _shim.js which selects a platform-specific binary (linux_x64, linux_arm64, darwin, win32), downloads it over HTTPS from hardcoded Cloudflare Workers hosts assembled from split-string arrays (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked-base64 fallback channel under *.sdk.dl.wel1.ru, writes the payload to /var/tmp or %TEMP% under a masquerade name (.cache_<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmods it 0o755, and spawns it detached via /bin/sh -c or cmd.exe with stdio ignored and unref(). No pinning, no hash or signature verification, no relationship between the downloaded binary and any stated package purpose. Hostnames and DNS domains are constructed from split-and-join arrays, and cache filenames plus in-code comments (analytics_state, telemetry, rate limit) provide cover-story misdirection.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ded-pwa-c-micro (version 35.8.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-pwa-c-micro across your stack and pipelines.
If you installed it — respond
Remove ded-pwa-c-micro 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.
Did it already run?
If ded-pwa-c-micro 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-micro 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-micro-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.