dolyame-ui-inputtagnpm
dolyame-ui-inputtag is a confirmed malicious npm package (MAL-2026-13585) 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-inputtag (npm)
What this malware does
On require of the package's main entry, index.js loads init.js which downloads a platform-specific executable from hardcoded oob-worker.*.workers.dev endpoints, with a DNS-TXT chunked fallback over *.dl.wel1.ru sub-domains (sdk/ext/pkg/net.dl.wel1.ru). The fetched binary is written to /tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmod 755'd, and spawned detached via /bin/sh -c or cmd.exe. Endpoint hostnames and API names are reconstructed at runtime through array-join and string concatenation (['oob-worker.','cf103-070.worker','s.de','v'].join(''), require('child_'+'process'), fs['chmod'+'Sync']) to evade static scanners. A second dropper path with the same shape is present in lib/telemetry.js, loaded via the package main. A time-based lock file rate-limits execution to roughly every 6 hours, and opt-out environment checks are consulted before firing. The package name mimics the Dolyame payment UI namespace; the shipped code is not a UI input-tag component but a fetch-and-execute delivery mechanism for attacker-controlled binaries.
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-inputtag (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-inputtag across your stack and pipelines.
If you installed it — respond
dolyame-ui-inputtag is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-inputtag, 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-inputtag 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-inputtag 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-inputtag-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.