ded-pwa-c-micronpm
Advisory published Updated
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
Search your lockfiles and build artifacts for ded-pwa-c-micro (version 35.8.3).
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 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
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.