Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

dolyame-ui-togglenpm

dolyame-ui-toggle is a confirmed malicious npm package (MAL-2026-13196) that typosquats a legitimate package to trick installs (malicious version 35.4.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-toggle (npm)

MAL-2026-13196
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dolyame-ui-toggle

What this malware does

Requiring the package loads ext.js, which downloads a platform-specific binary from obfuscated *.workers.dev endpoints (with a DNS-TXT base64 fallback via *.dl.wel1.ru), writes it to /var/tmp or %TEMP% under disguised names such as '.cache<tag>' or 'dotnet_diag_<tag>.exe', chmods it 0755, and spawns it detached via '/bin/sh -c' or 'cmd.exe /c start /b'. Endpoint hostnames and resolver domains are constructed by joining fragment arrays to evade string scans, and the dropped file names impersonate telemetry/diagnostic artifacts. The package's declared purpose is a trivial UI toggle; the fetched, unpinned, unverified binary is unrelated to that purpose. The result is arbitrary attacker-controlled code execution on any machine that installs or imports this version.

Malicious versions

1 flagged
35.4.1

Indicators of compromise (SHA-256)

e9a2d0e912bed4c7005a9945215406319204611c186b19d77065d1a5216e5fb1

Detection & response playbook

Typosquat
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-toggle (version 35.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-toggle across your stack and pipelines.

  2. If you installed it — respond

    dolyame-ui-toggle is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-toggle, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If dolyame-ui-toggle 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.

  4. How O3 protects you

    O3 blocks dolyame-ui-toggle 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-toggle on npm has been identified as a malicious package (version 35.4.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015579

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

dolyame-ui-toggle (npm) malicious package — MAL-2026-13196 | O3 Security