Which versions of dolyame-ui-swiper are malicious?

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

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

dolyame-ui-swiper carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

I already installed dolyame-ui-swiper — how do I know if it already compromised me?

If dolyame-ui-swiper was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dolyame-ui-swiper part of a known attack campaign?

Yes — dolyame-ui-swiper is associated with the IN-MAL-2026-015586 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-swiper across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dolyame-ui-swiper (version 35.7.7).

Malicious package

dolyame-ui-swipernpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

dolyame-ui-swiper is a confirmed malicious npm package (MAL-2026-13188) that runs destructive / sabotage code (malicious version 35.7.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-swiper (npm)

MAL-2026-13188

Immediate action

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

npm uninstall dolyame-ui-swiper

What this malware does

On require() of the package's main entry, bridge.js unconditionally runs an init() routine that selects an OS-specific target path, downloads an opaque native binary from one of several string-split-obfuscated Cloudflare Workers subdomains (oob-worker.cf100-416.workers.dev, cf101-adf, cf102-baf, cf103-070) with a DNS TXT chunked-base64 fallback via sdk.dl.wel1.ru, writes it under /tmp or %TEMP% with a disguised name (.cache<hex> or dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd /c start /b. Destination hostnames and the child_process identifier are assembled at runtime by joining string fragments to evade static inspection. The package is advertised as a UI component library; the fetched binary has no relationship to that stated purpose, is hosted on anonymous edge-worker infrastructure, is unpinned and unverified, and is executed with the privileges of the installing process. Requiring or installing the package results in arbitrary remote code execution on the installer's host.

Malicious versions

1 flagged

35.7.7

Indicators of compromise (SHA-256)

5d7b18729a9aed582b73ddcfb2c332aba97810caa9daea155e62fd4035158a8a

Detection & response playbook

Destructive / sabotage

Find it
Search your lockfiles and build artifacts for dolyame-ui-swiper (version 35.7.7).
If you installed it — respond
dolyame-ui-swiper carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If dolyame-ui-swiper was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dolyame-ui-swiper on npm has been identified as a malicious package (version 35.7.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015586

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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