Which versions of dolyame-ui-chart are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-chartnpm

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

Malicious code in dolyame-ui-chart (npm)

MAL-2026-13142

Immediate action

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

npm uninstall dolyame-ui-chart

What this malware does

On require() of the package, index.js loads shim.js which selects a platform-specific asset path, downloads a binary from one of four hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev) with DNS-TXT fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru. The fetched bytes are written to a temp path under decoy names (e.g. dotnet_diag<rand>.exe,.cache_<rand>), chmod 0755 on POSIX, and spawned detached via /bin/sh -c or cmd /c start. Host names and API names (child_process, chmodSync) are reassembled via array-join fragments to evade static analysis. A secondary dropper with equivalent base64-decode + chmod 755 + spawn '/bin/sh -c <file> &' logic is bundled in lib/telemetry.js (~81KB) under an 'analytics SDK' cover story. Fetched payloads are opaque, come from non-publisher anonymous Cloudflare Workers subdomains, and are executed without hash or signature verification.

Malicious versions

1 flagged

35.7.2

Indicators of compromise (SHA-256)

d74520fb069fe50500e9094c4e509d06ab266bda101111701e409951e08053e9

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

Campaign

IN-MAL-2026-015632

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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