dolyame-ui-inputcardnpm
dolyame-ui-inputcard is a confirmed malicious npm package (MAL-2026-13575) 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-inputcard (npm)
What this malware does
On require() of the package, shim.js and lib/telemetry.js (disguised as a Sentry-style APM SDK) select a platform-specific asset, fetch an opaque binary from one of three obfuscated Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, cf103-070.workers.dev, cf102-baf.workers.dev) with a DNS-TXT chunked-base64 fallback via *.dl.wel1.ru, write it to /var/tmp/.cache<rand> or %TEMP%\dotnet_diag_<rand>.exe, chmod 0755, and spawn it detached via /bin/sh -c or cmd. No hash or signature verification is performed. Endpoint hostnames and Node API names ('child_process', 'chmodSync', 'hostname') are constructed at runtime from split string fragments (.join('') and string concatenation) to evade static scanners. The destinations and delivery mechanism are unrelated to the package's stated UI-input-card purpose.
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-inputcard (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-inputcard across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-inputcard 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-inputcard 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-inputcard 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-inputcard-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.