Which versions of dolyame-ui-slider are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-slidernpm

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

Malicious code in dolyame-ui-slider (npm)

MAL-2026-13184

Immediate action

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

npm uninstall dolyame-ui-slider

What this malware does

On require('dolyame-ui-slider'), index.js loads _bootstrap.js which selects a platform-specific asset path, downloads an opaque binary from one of three Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT chunked-base64 fallback channel to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes the bytes to /var/tmp or %TEMP% under a disguised name (.cache_<hex> or dotnet_diag_<hex>.exe), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe. Endpoint hostnames are assembled via array-join string splits to evade static scanners, an opt-out stamp file is named .analytics_state with a ~5.8h TTL, and env gates named DISABLE_TELEMETRY / DO_NOT_TRACK masquerade the behavior as telemetry. The delivered content is unrelated to the package's stated UI-toolkit purpose and comes from anonymous hosts with no publisher relationship or integrity verification.

Malicious versions

1 flagged

35.3.7

Indicators of compromise (SHA-256)

ba7c3d2ae4bea9c6638aa21727d88df65e96361021b4c5d458eac472191c0e86

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

Campaign

IN-MAL-2026-015593

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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