What does the dolyame-ui-accordion malware do?

The package is advertised as a React accordion UI component but on require() unconditionally loads _vendor.js, which downloads a platform-specific binary from obfuscated Cloudflare workers.dev endpoints (with a DNS TXT-record base64 fallback via *.wel1.ru), writes it to /tmp or %TEMP% under disguised names (.cache_ on Unix, dotnet_diag_ .exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe. Destination hostnames are assembled at runtime from split string fragments (e.g. ["oob-worker.cf99-9b3.workers",".dev"].join("")) to evade static inspection, and the cover naming ("analytics_state", "dotnet_diag_*", opt-out env vars like DISABLE_TELEMETRY / ANALYTICS_OPT

Which versions of dolyame-ui-accordion are malicious?

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

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

dolyame-ui-accordion is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

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

Malicious package

dolyame-ui-accordionnpm

dolyame-ui-accordion is a confirmed malicious npm package (MAL-2026-13133) that steals credentials and exfiltrates sensitive data (malicious version 35.2.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-accordion (npm)

MAL-2026-13133

Immediate action

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

npm uninstall dolyame-ui-accordion

What this malware does

The package is advertised as a React accordion UI component but on require() unconditionally loads vendor.js, which downloads a platform-specific binary from obfuscated Cloudflare workers.dev endpoints (with a DNS TXT-record base64 fallback via *.wel1.ru), writes it to /tmp or %TEMP% under disguised names (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe. Destination hostnames are assembled at runtime from split string fragments (e.g. ["oob-worker.cf99-9b3.workers",".dev"].join("")) to evade static inspection, and the cover naming ("analytics_state", "dotnet_diag_*", opt-out env vars like DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK) frames the flow as diagnostics. The advertised UI-accordion purpose does not justify any runtime download or native execution.

Malicious versions

1 flagged

35.2.6

Indicators of compromise (SHA-256)

9a72f168a8501a4518ddfc5cdda24be49bfa8effefbf72fa490bbaa57daa3637

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-accordion (version 35.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-accordion across your stack and pipelines.
If you installed it — respond
dolyame-ui-accordion is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dolyame-ui-accordion 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-accordion 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-accordion on npm has been identified as a malicious package (version 35.2.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015645

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-accordion-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database