ded-aa-liza-ded-aa-liza-corenpm
ded-aa-liza-ded-aa-liza-core is a confirmed malicious npm package (MAL-2026-13124) that typosquats a legitimate package to trick installs (malicious version 35.2.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ded-aa-liza-ded-aa-liza-core (npm)
What this malware does
On require() of ded-aa-liza-ded-aa-liza-core, index.js loads ext.js which downloads a platform-specific binary from hardcoded Cloudflare Workers endpoints (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS TXT fallback channel to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. Destination hostnames are assembled at runtime by joining fragmented substring arrays (e.g. ["oob-wor","ker.cf103-070.workers.de","v"].join("")) rather than appearing as plain literals. The fetched payload is written to /var/tmp or %TEMP% under names disguised to mimic diagnostic tools (.cache<hex>, dotnet_diag_<hex>.exe), made executable via fs.chmodSync(0o755), and spawned detached through /bin/sh -c or cmd. The package is advertised as foundational type definitions but performs no such function; the only import-time effect is dropping and executing an opaque remote binary on the installer's host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ded-aa-liza-ded-aa-liza-core (version 35.2.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-aa-liza-ded-aa-liza-core across your stack and pipelines.
If you installed it — respond
ded-aa-liza-ded-aa-liza-core is a typosquat — you almost certainly intended a legitimately-named package. Remove ded-aa-liza-ded-aa-liza-core, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If ded-aa-liza-ded-aa-liza-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.
How O3 protects you
O3 blocks ded-aa-liza-ded-aa-liza-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks ded-aa-liza-ded-aa-liza-core-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.