What does the dolyame-ui-dropdown malware do?

On require('dolyame-ui-dropdown'), index.js loads _helpers.js which selects a platform-specific endpoint from an obfuscated (split-literal) host list including oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, and oob-worker.cf100-416.workers.dev, with a DNS-TXT chunked fallback that assembles a base64 payload from c. and numbered n. TXT records under dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The downloaded binary is written to /var/tmp or %TEMP% under cover-story names such as.cache_ or dotnet_diag_ .exe, chmodded to 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp+' &']).unref(). Obfuscation includes s

Which versions of dolyame-ui-dropdown are malicious?

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

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

Remove dolyame-ui-dropdown 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-dropdown — how do I know if it already compromised me?

If dolyame-ui-dropdown 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-dropdown part of a known attack campaign?

Yes — dolyame-ui-dropdown is associated with the IN-MAL-2026-015619 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-dropdown 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-dropdown (version 35.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-dropdown across your stack and pipelines.

Malicious package

dolyame-ui-dropdownnpm

dolyame-ui-dropdown is a confirmed malicious npm package (MAL-2026-13152) that executes malicious code on install (malicious version 35.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-dropdown (npm)

MAL-2026-13152

Immediate action

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

npm uninstall dolyame-ui-dropdown

What this malware does

On require('dolyame-ui-dropdown'), index.js loads helpers.js which selects a platform-specific endpoint from an obfuscated (split-literal) host list including oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, and oob-worker.cf100-416.workers.dev, with a DNS-TXT chunked fallback that assembles a base64 payload from c.<domain> and numbered n.<domain> TXT records under dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The downloaded binary is written to /var/tmp or %TEMP% under cover-story names such as.cache<hex> or dotnet_diag_<hex>.exe, chmodded to 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp+' &']).unref(). Obfuscation includes string-splitting of the child_process require ('child_' + 'process'), array-join reassembly of destination hostnames, and reflective property access such as fs['chmod'+'Sync']. A second dropper stage with the same primitives is shipped in lib/telemetry.js. A package advertised as a UI dropdown has no legitimate reason to fetch and execute platform-specific ELF/Mach-O/EXE payloads at import time.

Malicious versions

1 flagged

35.6.2

Indicators of compromise (SHA-256)

78e2cf3af799e05f20494aba04b5d85aa1335bce541af4cb13aa715a2cda6ea5

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-dropdown (version 35.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-dropdown across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-dropdown 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-dropdown 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-dropdown 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-dropdown on npm has been identified as a malicious package (version 35.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015619

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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