dolyame-ui-moneynpm
dolyame-ui-money is a confirmed malicious npm package (MAL-2026-13169) that executes malicious code on install (malicious version 35.6.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-money (npm)
What this malware does
On require() of this package, index.js unconditionally loads bridge.js, which downloads a platform-specific native executable from Cloudflare Workers hosts whose names are assembled at runtime via array.join("") (e.g. oob-worker.cf102-baf.workers.dev and siblings), with a DNS-TXT base64 chunked fallback resolved through *.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache<rand> on Unix or %TEMP%\dotnet_diag_<rand>.exe on Windows, chmod 0755, and spawned detached via /bin/sh -c or cmd.exe. A /tmp state file (.analytics_state) throttles re-execution and DO_NOT_TRACK is honored to suppress the behavior in inspection environments. The package's declared purpose ("React components / UI toolkit") is unrelated to any of this. Hostname obfuscation, cover-story file names (dotnet_diag_*.exe), the DNS-TXT covert channel, and the research-evasion check together establish hostile intent; the dropped binary is opaque attacker-controlled code executed with the installer's privileges on every require().
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-money (version 35.6.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-money across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-money 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-money 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-money 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-money-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.