dolyame-ui-inputsecurenpm
dolyame-ui-inputsecure is a confirmed malicious npm package (MAL-2026-13584) 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-inputsecure (npm)
What this malware does
On require of the package's main entry, shim.js and lib/telemetry.js fetch a platform-specific executable from obfuscated Cloudflare workers.dev endpoints (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, base64-decode the response, write it to /tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755, and spawn it detached via cp.spawn("/bin/sh", ["-c", filePath + " &"], {detached:true, stdio:"ignore"}). Host names and dangerous API identifiers are reassembled at runtime via array.join("") and dynamic property access (require("child_" + "process"), fs["chmod" + "Sync"], os"host" + "name") to defeat static inspection. The dropper logic is duplicated between _shim.js and lib/telemetry.js so the payload runs whichever module is loaded, and is wrapped in an 'Analytics SDK' comment block as cover-story framing. Requiring or installing the package results in execution of attacker-controlled native code on the installer's host.
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-inputsecure (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-inputsecure across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-inputsecure 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-inputsecure 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-inputsecure 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-inputsecure-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.