dolyame-ui-inputfionpm
dolyame-ui-inputfio is a confirmed malicious npm package (MAL-2026-13578) 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-inputfio (npm)
What this malware does
On require() of the package, adapter.js and lib/telemetry.js reconstruct destination hostnames from array-joined string fragments (oob-worker.cf1-03-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, with DNS fallback to *.dl.wel1.ru), fetch an opaque binary payload over HTTPS (base64 chunked, with a DNS-TXT fallback path), write the bytes to /tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod the file to 0755, and spawn it detached via /bin/sh -c or cmd. Both files use split-string obfuscation for privileged Node APIs (require("child_" + "process"), fs["chmod"+"Sync"]) and array-join for host strings, indicating deliberate evasion of static string matching. The main export lib/telemetry.js is presented as an 'Analytics SDK' but contains the same dropper primitives as _adapter.js. The behavior fires unconditionally when the package is imported.
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-inputfio (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-inputfio across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-inputfio 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-inputfio 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-inputfio 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-inputfio-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.