Malicious code in ded-pwa-c-mapping (npm)
The npm package ded-pwa-c-mapping contained malicious code that downloads and executes unsigned native binaries from attacker-controlled infrastructure upon package import. The attack uses obfuscated hostnames, DNS-TXT fallback channels, and environment variable checks to evade detection.
- Disclosed
- Last updated
- Blast radius
- Any npm consumer of ded-pwa-c-mapping
- Ecosystems
- Attack vectors
- Affected entities
- ded-pwa-c-mappingnpm package containing malicious code
The npm package ded-pwa-c-mapping was found to contain malicious code in its helpers.js file. Upon package import, the code executes a bootstrap routine that selects a platform-specific payload and fetches an opaque native binary over HTTPS from attacker-controlled *.workers.dev hosts (oob-worker.cf100-416.workers.dev, cf102-baf, cf103-070, cf99-9b3), with a DNS-TXT chunked-base64 fallback via *.dl.wel1.ru.\n\nThe malicious code writes the downloaded binary to /var/tmp or %TEMP% under disguised names (.cache or dotnet_diag_.exe), sets executable permissions (0755), and spawns it detached via /bin/sh -c or cmd /c start. Hostnames are assembled at runtime by joining fragments to defeat string-based scanners. An a.analytics_state marker file throttles re-execution, and the code references DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, and DO_NOT_TRACK environment variables to frame the behavior as telemetry.\n\nNo hash or signature verification is performed on the downloaded payload before execution. The attack was discovered by Amazon Inspector and credited to the OpenSSF malicious-packages project.
Indicators of compromise
- Packages
- ded-pwa-c-mapping
- Domains
- oob-worker.cf100-416.workers.dev
- cf102-baf.workers.dev
- cf103-070.workers.dev
- cf99-9b3.workers.dev
- dl.wel1.ru
Remediation
- Remove ded-pwa-c-mapping from all projects immediately
- Audit npm package.lock or yarn.lock files for any version of ded-pwa-c-mapping
- Review process execution logs and network traffic for connections to *.workers.dev or *.dl.wel1.ru domains
- Inspect /var/tmp and %TEMP% directories for suspicious files matching .cache_ or dotnet_diag_ patterns
- Regenerate any credentials or secrets that may have been exposed on affected systems
- Update to a patched version if available, or use an alternative package
Sources
- GitHub Advisory GHSA-6m24-ppw5-qfm9 · GitHub Advisory Database
Cite this entry
"Malicious code in ded-pwa-c-mapping (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-ded-pwa-c-mapping-npm-1j45yd
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package