Which versions of dolyame-ui-carouselline are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-carousellinenpm

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

Malicious code in dolyame-ui-carouselline (npm)

MAL-2026-13556

Immediate action

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

npm uninstall dolyame-ui-carouselline

What this malware does

On require() of the package, index.js loads support.js and lib/telemetry.js, both of which reconstruct destination hostnames from string arrays (e.g. oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev) and DNS-TXT resolvers (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), fetch a platform-specific executable payload over HTTPS with a base64 DNS-TXT fallback channel, write the bytes to /var/tmp or %TEMP% under a cover-story filename (.cache<hex> or dotnet_diag_<hex>.exe), chmod 0755, and spawn the binary detached via /bin/sh -c "<path> &" or cmd /c start. Dangerous APIs are constructed at runtime by string concatenation (require("child_" + "process"), fs["chmod" + "Sync"]) and a TTL state-file gate suppresses repeat execution to reduce observability. lib/telemetry.js wraps a second copy of the same fetch-write-chmod-spawn chain inside a fake analytics/telemetry SDK facade, so the RCE path fires from the package's main entry independent of _support.js.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

f7712f1618991466bc33076081db37dd883be10f4c0c4308fe66216cece89a03

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

Campaign

IN-MAL-2026-017008

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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