dolyame-ui-inputmoneynpm
dolyame-ui-inputmoney is a confirmed malicious npm package (MAL-2026-13579) that typosquats a legitimate package to trick installs (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-inputmoney (npm)
What this malware does
On require of the package, index.js loads support.js, which fetches a platform-specific binary from string-split Cloudflare Worker hostnames (oob-worker.cf10{1,2,3}-*.workers.dev), writes it under /var/tmp/.cache<hex> or Windows Temp as dotnet_diag_<hex>.exe, chmods it 0755, and spawns it detached via /bin/sh -c '<file> &' (or cmd on Windows). When the workers.dev endpoints are unreachable, support.js falls back to a DNS TXT covert channel against sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, reassembling a base64 payload from chunked TXT records. lib/telemetry.js implements a parallel drop-and-execute path under an 'analytics SDK' framing, using base64-decoded buffers, fs['chmod'+'Sync'] to 0755, and cp.spawn('/bin/sh', ['-c', filePath+' &']). Hostnames, endpoint paths, and the child_process import are constructed with string-split/concatenation (require('child'+'process'), ['oob-worker.cf103-0','70.workers.dev'].join('')) to evade static detection. The staging filename (dotnet_diag_<hex>.exe) mimics system tooling, the destinations are not the package publisher, and the fetched bytes are unpinned and unverified.
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-inputmoney (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-inputmoney across your stack and pipelines.
If you installed it — respond
dolyame-ui-inputmoney is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-inputmoney, 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-inputmoney 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-inputmoney 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-inputmoney-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.