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

dolyame-ui-layoutnpm

dolyame-ui-layout is a confirmed malicious npm package (MAL-2026-13163) that typosquats a legitimate package to trick installs (malicious version 35.9.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-layout (npm)

MAL-2026-13163
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dolyame-ui-layout

What this malware does

On every require() of dolyame-ui-layout, index.js loads platform.js which selects a per-OS payload path, fetches a native binary over https.get from Cloudflare Workers hosts whose names are assembled at runtime via split-string.join() concatenation (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked-base64 fallback under *.dl.wel1.ru. The downloaded bytes are written to /tmp or %TEMP% under names impersonating system diagnostics (.cache<hex>, dotnet_diag_<hex>.exe), chmod'd to 0755, and detach-spawned via spawn("/bin/sh",["-c", path+" &"], {detached:true}).unref() on POSIX or cmd on Windows. Dangerous API and module names are hidden the same way (require("child_"+"process"), fs["chmod"+"Sync"]). A second file lib/telemetry.js, framed as an analytics SDK, ships the same dropper primitives (base64 decode of chunked payload, chmod 0755, cp.spawn("/bin/sh",...)) as redundant attack infrastructure. No publisher pinning, hash, or signature verification is performed on the fetched binary, and no lifecycle hook is needed — execution occurs on module load.

Malicious versions

1 flagged
35.9.8

Indicators of compromise (SHA-256)

8f8bf970c387898705de052ea5736f3f90877cfcdad204af1a772b5230c95c31

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

  2. If you installed it — respond

    dolyame-ui-layout is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-layout, 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 dolyame-ui-layout 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 dolyame-ui-layout 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. dolyame-ui-layout on npm has been identified as a malicious package (version 35.9.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015614

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-layout-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

dolyame-ui-layout (npm) malicious package — MAL-2026-13163 | O3 Security