dolyame-ui-clickablenpm
dolyame-ui-clickable is a confirmed malicious npm package (MAL-2026-13145) that executes malicious code on install (malicious version 35.6.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-clickable (npm)
What this malware does
On require() of the package, index.js unconditionally loads init.js, which selects a platform-specific endpoint (linux_x64, linux_arm64, darwin, win32) and downloads a native binary from a rotating list of anonymous Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS TXT fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache<hex> or %TEMP%/dotnet_diag_<hex>.exe, chmod'd 0755, and spawned detached via cp.spawn("/bin/sh", ["-c", fp + " &"], {detached:true}) or the Windows equivalent. Hostnames and sensitive API names (child_process, chmodSync) are reassembled at runtime from split string arrays to evade static matching, and the code is framed with cover-story comments as analytics/telemetry. A second, ~81 KB copy of the same fetch-and-execute pattern ships in lib/telemetry.js, using the same string-split evasion and a base64-decoded payload piped to /bin/sh with chmod 0755. The declared purpose (a UI-components package) has no need for native binary execution from anonymous infrastructure.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-clickable (version 35.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-clickable across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-clickable from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dolyame-ui-clickable 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 dolyame-ui-clickable 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 dolyame-ui-clickable-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.