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

ded-aa-liza-ui-componentsnpm

ded-aa-liza-ui-components is a confirmed malicious npm package (MAL-2026-12672) that typosquats a legitimate package to trick installs (malicious version 35.8.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ded-aa-liza-ui-components (npm)

MAL-2026-12672
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ded-aa-liza-ui-components

What this malware does

On require() of this package, index.js loads helpers.js which downloads a per-platform native executable (linux_x64, linux_arm64, darwin, win32) from attacker-controlled Cloudflare *.workers.dev endpoints (oob-worker.cf100-416.workers.dev, cf101-adf.workers.dev, cf99-9b3.workers.dev) with a DNS-TXT base64 fallback under *.dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The downloaded bytes are written to /var/tmp or %TEMP% under disguised names (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached via spawn("/bin/sh", ["-c", fp+" &"], {detached:true}) or spawn("cmd",...). Destination hostnames are reconstructed at runtime by splitting/joining string fragments (e.g. ["oob-worker.cf101-adf",".workers.d","ev"].join("")) to evade static analysis. Comments and env-var checks (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) mimic telemetry as cover. The advertised purpose is a React UI components library, which does not require fetching and executing native binaries from third-party Cloudflare Workers infrastructure.

Malicious versions

1 flagged
35.8.7

Indicators of compromise (SHA-256)

a328f8fbefe24a810c8fe1c0249029992137bec024cab060df03d88347b5185b

Detection & response playbook

Typosquat
  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-liza-ui-components (version 35.8.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ded-aa-liza-ui-components across your stack and pipelines.

  2. If you installed it — respond

    ded-aa-liza-ui-components is a typosquat — you almost certainly intended a legitimately-named package. Remove ded-aa-liza-ui-components, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If ded-aa-liza-ui-components 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-liza-ui-components 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-liza-ui-components on npm has been identified as a malicious package (version 35.8.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015100

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ded-aa-liza-ui-components-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.

Explore