dolyame-ui-contextmenunpm
Advisory published Updated
dolyame-ui-contextmenu is a confirmed malicious npm package (MAL-2026-13561) that executes malicious code on install (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-contextmenu (npm)
What this malware does
On require() of the package, polyfill.js downloads a platform-specific binary from hardcoded Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), writes it to a temp path under cover-story names such as 'dotnet_diag.exe' and '.cache_', chmods it 0755, and spawns it detached via cmd.exe or /bin/sh. Destination hostnames are assembled from array fragments (e.g. ["oob-w","orker.cf99-9b3.workers.de","v"].join("")) to evade static scanners, and a base64-over-DNS-TXT covert channel under *.dl.wel1.ru is used to fetch the payload when HTTPS is blocked. The destinations are anonymous Workers subdomains unrelated to any documented purpose of the package, and the delivered bytes are opaque attacker-controlled code executed on the installer's host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for dolyame-ui-contextmenu (version 35.8.1).
If you installed it — respond
Remove dolyame-ui-contextmenu 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-contextmenu was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks dolyame-ui-contextmenu-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.