What does the dolyame-ui-inputpassword malware do?

On require of the package, index.js loads lib/telemetry.js which, together with _bootstrap.js, fetches a platform-specific binary from a rotating list of anonymous Cloudflare Workers hosts (oob-worker.cf1{00,01,02,03}-*.workers.dev) with a DNS-TXT covert-channel fallback under sdk.dl.wel1.ru (chunk count from c. , base64 chunks from indexed TXT records reassembled via Buffer.from(..., 'base64')). The fetched bytes are written to a disguised temp path (.cache_ /dotnet_diag_ .exe), chmodded to 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. Destination hostnames and module names are assembled from split string fragments (e.g. 'oob-worker.cf103-070.wo'+'rkers.d'+'e

Which versions of dolyame-ui-inputpassword are malicious?

The following npm versions of dolyame-ui-inputpassword are flagged malicious: 35.8.1. Treat any of these as compromised.

How do I remediate dolyame-ui-inputpassword if I installed it?

Remove dolyame-ui-inputpassword 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.

I already installed dolyame-ui-inputpassword — how do I know if it already compromised me?

If dolyame-ui-inputpassword 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.

Is dolyame-ui-inputpassword part of a known attack campaign?

Yes — dolyame-ui-inputpassword is associated with the IN-MAL-2026-016894 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dolyame-ui-inputpassword across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-inputpassword (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-inputpassword across your stack and pipelines.

Malicious package

dolyame-ui-inputpasswordnpm

dolyame-ui-inputpassword is a confirmed malicious npm package (MAL-2026-13508) 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-inputpassword (npm)

MAL-2026-13508

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dolyame-ui-inputpassword

What this malware does

On require of the package, index.js loads lib/telemetry.js which, together with bootstrap.js, fetches a platform-specific binary from a rotating list of anonymous Cloudflare Workers hosts (oob-worker.cf1{00,01,02,03}-*.workers.dev) with a DNS-TXT covert-channel fallback under sdk.dl.wel1.ru (chunk count from c.<domain>, base64 chunks from indexed TXT records reassembled via Buffer.from(..., 'base64')). The fetched bytes are written to a disguised temp path (.cache<hex>/dotnet_diag_<hex>.exe), chmodded to 0755, and spawned detached via /bin/sh -c or cmd.exe /c start. Destination hostnames and module names are assembled from split string fragments (e.g. 'oob-worker.cf103-070.wo'+'rkers.d'+'ev', require('child_'+'process'), fs['chmod'+'Sync']) to evade static string search. The package presents itself as a UI input-password wrapper; the dropper behavior is unrelated to that stated purpose and is duplicated across _bootstrap.js and lib/telemetry.js so it fires whether the package is loaded via the main entry or the bootstrap side-effect.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

fbe3efece732cd0eab0df9c3fa387540804b7a1f7a911a340c3852e7f2c54674

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-inputpassword (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-inputpassword across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-inputpassword 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-inputpassword 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-inputpassword 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

No. dolyame-ui-inputpassword on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016894

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-inputpassword-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database