Which versions of dolyame-ui-pie are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-pienpm

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

Malicious code in dolyame-ui-pie (npm)

MAL-2026-13173

Immediate action

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

npm uninstall dolyame-ui-pie

What this malware does

Requiring the package triggers async initialization in support.js that downloads a platform-specific binary (linux x64/arm64, darwin, win32) from Cloudflare Workers hosts and *.dl.wel1.ru mirrors whose hostnames are assembled at runtime via array.join("") string splits, with a DNS-TXT fallback resolver for the same domain family (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The fetched bytes are written to /var/tmp/.cache<rand> on Unix or TEMP/dotnet_diag_<rand>.exe on Windows, chmodded 0755, and spawned detached via /bin/sh -c or cmd /c start. child_process is loaded via require("child_" + "process") and fs.chmodSync via fs["chmod" + "Sync"] to evade static scanners. The package advertises itself as a React UI component library; none of this behavior relates to that purpose. Attacker-controlled binaries with disguised on-disk names (dotnet_diag,.cache_) execute on every require() of the package.

Malicious versions

1 flagged

35.5.3

Indicators of compromise (SHA-256)

6f473b4f8898130c8b57fd3a129bf81a38b449ea8970e58a6e4c486943eb5579

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

Campaign

IN-MAL-2026-015603

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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