dolyame-ui-badgenpm
dolyame-ui-badge is a confirmed malicious npm package (MAL-2026-13136) that executes malicious code on install (malicious version 35.4.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-badge (npm)
What this malware does
On require() of dolyame-ui-badge, the package loads bootstrap.js which downloads a native binary from runtime-assembled Cloudflare Workers hosts (oob-worker.cf10{1,2,3}-*.workers.dev) with a DNS TXT-record fallback channel over *.dl.wel1.ru, writes it to /tmp or %TEMP% under disguised names such as dotnet_diag.exe and.cache_, chmods it to 0o755, and spawns it detached via /bin/sh -c or cmd.exe /c start. Destination hostnames are obfuscated by splitting them across array elements and reconstructing at runtime via.join(""). Cover-story comments referencing SHA-256 verification, opt-out flags, and rate-limiting do not correspond to matching code. The package advertises itself as a UI badge component and has no build-time or functional need for a native binary. No signature or hash verification is performed on the downloaded payload.
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-badge (version 35.4.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-badge across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-badge 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-badge 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-badge 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-badge-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.