Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

ded-aa-common-ded-aa-common-corenpm

ded-aa-common-ded-aa-common-core is a confirmed malicious npm package (MAL-2026-13123) that opens a backdoor for remote access (malicious version 35.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ded-aa-common-ded-aa-common-core (npm)

MAL-2026-13123
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ded-aa-common-ded-aa-common-core

What this malware does

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.

Malicious versions

1 flagged
35.1.6

Indicators of compromise (SHA-256)

30a80297ae44091b682bf8fa68610f345348813d94b2c84e7f82a3183b938a94

Detection & response playbook

Backdoor / remote access

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ded-aa-common-ded-aa-common-core (version 35.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-aa-common-ded-aa-common-core across your stack and pipelines.

  2. If you installed it — respond

    ded-aa-common-ded-aa-common-core establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If ded-aa-common-ded-aa-common-core 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.

  4. How O3 protects you

    O3 blocks ded-aa-common-ded-aa-common-core 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

No. ded-aa-common-ded-aa-common-core on npm has been identified as a malicious package (version 35.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015638

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ded-aa-common-ded-aa-common-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
ded-aa-common-ded-aa-common-core (npm) malicious package — MAL-2026-13123 | O3 Security