dolyame-ui-notificationnpm
dolyame-ui-notification is a confirmed malicious npm package (MAL-2026-13171) that typosquats a legitimate package to trick installs (malicious version 35.5.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-notification (npm)
What this malware does
Package advertises itself as a UI notification toolkit but its main entry require()s./compat.js, which on load randomly selects a destination from four obfuscated Cloudflare workers.dev hosts (oob-worker.cf9-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev) reconstructed at runtime from split string arrays, with a DNS-TXT fallback channel over *.dl.wel1.ru (sdk./ext./pkg./net.dl.wel1.ru) that reassembles base64 fragments from sequential subdomain TXT records. It downloads a platform-specific native binary (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), writes it to /var/tmp/.cache<hex> or %TEMP%\dotnet_diag_<hex>.exe under a cover-story filename, chmods 0755, and spawns it detached via /bin/sh or cmd. The runtime-reconstructed destinations, DNS-TXT covert channel, hidden staging paths with diagnostic-tool-lookalike filenames, and mismatch between the declared UI purpose and the fetch-and-execute behavior identify this as a supply-chain dropper rather than legitimate functionality.
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 dolyame-ui-notification (version 35.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-notification across your stack and pipelines.
If you installed it — respond
dolyame-ui-notification is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-notification, 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 dolyame-ui-notification 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-notification 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-notification-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.