MAL-2026-13123 Malicious code in ded-aa-common-ded-aa-common-core (npm)
Malicious package
Published
MAL-2026-13123 is a malicious package: ded-aa-common-ded-aa-common-core (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-13123/ (Markdown: https://insights.sbomify.com/MAL-2026-13123/index.md)
- Package
- ded-aa-common-ded-aa-common-core
- Registry
- npm
What is MAL-2026-13123?
MAL-2026-13123 is a malicious package in ded-aa-common-ded-aa-common-core, published on 5 Aug 2026.
Official description
On require() of the package, index.js loads ext.js which fetches an opaque platform-specific binary from hardcoded Cloudflare Workers hosts (oob-worker.cf101/cf102/cf103-*.workers.dev), writes it to /tmp or %TEMP% under a disguised name (dotnet_diag.exe on Windows,.cache_ on Unix), chmods 0755, and spawns it detached via cmd.exe/start or /bin/sh -c with stdio ignored and unref(). C2 hostnames and fallback domains are assembled from split-and-join string arrays to evade static analysis (e.g. ['sd','k.d','l.w','el1.','ru'].join('')). If HTTPS retrieval fails, the code reassembles the payload from base64-encoded DNS TXT records under *.dl.wel1.ru (sdk.dl.wel1.ru) via dns.resolveTxt and Buffer.from(…,'base64'), providing a covert channel resilient to endpoint/firewall filtering. A marker file analytics_state/.analytics_state provides TTL suppression to hide repeated executions. No hash or signature verification of the fetched payload; the child_process module is imported inside the activation path to further hinder static analysis.
What should I do about MAL-2026-13123?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.