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

dolyame-ui-linknpm

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

Malicious code in dolyame-ui-link (npm)

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

What this malware does

index.js requires./loader on load. loader.js reconstructs attacker-controlled hostnames from split string fragments joined via.join("") to yield Cloudflare Workers hosts oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev and oob-worker.cf102-baf.workers.dev, and a DNS-TXT fallback channel under subdomains of wel1.ru. It HTTPS-GETs a platform-specific binary (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), writes it to /var/tmp/.cache<hex> or %TEMP%\dotnet_diag<hex>.exe under a disguised filename, chmods 0755, and spawns it detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. lib/telemetry.js carries the same drop-and-exec primitives under an "analytics SDK" cover story. Fires automatically on require of the package, giving arbitrary native code execution on the installer's host.

Malicious versions

1 flagged
35.8.5

Indicators of compromise (SHA-256)

26aae43ae2f260593e90c501c2863a515d4aa4f6753fccf82df101c62d43b77a

Detection & response playbook

Malicious package
  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-link (version 35.8.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-link across your stack and pipelines.

  2. If you installed it — respond

    Remove dolyame-ui-link 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.

  3. Did it already run?

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

Campaign

IN-MAL-2026-015609

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-link-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-link (npm) malicious package — MAL-2026-13164 | O3 Security