dolyame-ui-inputphonenpm
dolyame-ui-inputphone is a confirmed malicious npm package (MAL-2026-13580) 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-inputphone (npm)
What this malware does
On require() of the package, index.js loads runtime.js which downloads a platform-specific binary from a set of Cloudflare Workers endpoints (oob-worker.cf10x-*.workers.dev) with a DNS-TXT chunked fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. Host strings are reconstructed at runtime via array-join (e.g. ['sdk.dl.wel1','.ru'].join('')) to evade static scans, and API references are split (child'+'process, 'chmod'+'Sync'). The fetched bytes are written to a temp path with a cover-story filename (.cache_, dotnet_diag_.exe), chmod 0755 on Unix, and executed detached via cp.spawn('/bin/sh',['-c', filePath+' &']) or spawn('cmd',...) on Windows. No hash or signature verification is performed and the destinations are unrelated to the declared publisher. The package's own main export lib/telemetry.js, presented as a Sentry-like analytics SDK, wraps the same download/write/chmod/spawn primitives — the telemetry facade is cover for the dropper.
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-inputphone (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-inputphone across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-inputphone 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-inputphone 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-inputphone 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-inputphone-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.