dolyame-ui-eventoutsidenpm
dolyame-ui-eventoutside is a confirmed malicious npm package (MAL-2026-13568) 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-eventoutside (npm)
What this malware does
On require() of dolyame-ui-eventoutside, bootstrap.js selects a platform-specific URL, downloads a binary from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf*.workers.dev) with a DNS-TXT-based fallback channel via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes the payload to a disguised temp path (Windows: dotnet_diag<hex>.exe; Unix:.cache_<hex>), chmods it 0755, and spawns it detached and unref'd through cmd.exe or /bin/sh. Destination hostnames are reassembled from split-string arrays (e.g. ["oob-worker.cf103-070.wo","rke","rs.de","v"].join("")) to defeat static inspection, and the dropped file is named to masquerade as a.NET diagnostics artifact (dotnet_diag_) or a hidden cache file (.analytics_state /.cache_). The package's advertised purpose is API client wrappers; fetching and executing arbitrary attacker-controlled binaries is unrelated to that purpose and gives the publisher arbitrary code execution on any machine that installs or imports the package.
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-eventoutside (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-eventoutside across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-eventoutside 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-eventoutside 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-eventoutside 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-eventoutside-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.