What does the dolyame-ui-block malware do?

On require of the package's main entry (index.js), _adapter.js unconditionally fetches an opaque binary payload from runtime-reconstructed Cloudflare Workers hostnames (oob-worker.cf1{00-03}-*.workers.dev) with a DNS-TXT-based fallback loader under *.dl.wel1.ru. The payload is written to a hidden path in /tmp or %TEMP% under a disguised name (.cache_ on POSIX, dotnet_diag_ .exe on Windows), marked executable with chmod 0755, and launched via a detached spawn of /bin/sh -c or cmd. No hash or signature verification is performed. Endpoint hostnames are assembled via array split/join to evade static string matching, and a DNS-TXT channel reads a base64-encoded payload split across numbe

Which versions of dolyame-ui-block are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-blocknpm

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

Malicious code in dolyame-ui-block (npm)

MAL-2026-13137

Immediate action

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

npm uninstall dolyame-ui-block

What this malware does

On require of the package's main entry (index.js), adapter.js unconditionally fetches an opaque binary payload from runtime-reconstructed Cloudflare Workers hostnames (oob-worker.cf1{00-03}-*.workers.dev) with a DNS-TXT-based fallback loader under *.dl.wel1.ru. The payload is written to a hidden path in /tmp or %TEMP% under a disguised name (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), marked executable with chmod 0755, and launched via a detached spawn of /bin/sh -c or cmd. No hash or signature verification is performed. Endpoint hostnames are assembled via array split/join to evade static string matching, and a DNS-TXT channel reads a base64-encoded payload split across numbered TXT records at 0..N.<resolver-domain>. Re-execution is gated by a timestamp file at /tmp/.analytics_state. The behavior has no relationship to a UI-components package and matches an install/import-time remote code execution dropper with deliberate obfuscation and evasion.

Malicious versions

1 flagged

35.1.8

Indicators of compromise (SHA-256)

7d0fed433faae413825a41330dcf81ec06db856008fdf7ebb4cd3e385626b4ce

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

Campaign

IN-MAL-2026-015647

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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