ded-pwa-bnpl-forms-demonpm
ded-pwa-bnpl-forms-demo is a confirmed malicious npm package (MAL-2026-12675) that executes malicious code on install (malicious version 35.9.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ded-pwa-bnpl-forms-demo (npm)
What this malware does
On require of the package, index.js loads support.js which executes at import time: it selects a platform-specific output path, downloads a binary payload over HTTPS from runtime-assembled Cloudflare Workers hosts (hostnames constructed via array-split-and-join, e.g. ['oob-','worker.cf101-adf.worker','s.dev'].join('')), with a fallback that queries DNS TXT records under *.dl.wel1.ru (hostnames similarly reconstructed from ['sdk.dl.','we','l1.','ru'].join('')), reads a chunk count from c.<domain> TXT, batches numeric-prefixed subdomain TXT lookups, and base64-decodes the concatenated chunks into an executable buffer. The payload is written to /var/tmp or %TEMP% under disguised names (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmod 0755 is applied on POSIX, and the binary is spawned detached via /bin/sh -c '<path> &' or cmd.exe /c start /b, with a.analytics_state marker file used to suppress re-runs. Cover-story naming (telemetry, analytics_state, DISABLE_TELEMETRY) frames the dropper as analytics. Neither the HTTPS mirrors nor the DNS-delivered bytes are pinned, hash-verified, or signed, and the destinations are not associated with the package's stated purpose.
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-bnpl-forms-demo (version 35.9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-pwa-bnpl-forms-demo across your stack and pipelines.
If you installed it — respond
Remove ded-pwa-bnpl-forms-demo 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-bnpl-forms-demo 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-bnpl-forms-demo 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-bnpl-forms-demo-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.