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

dolyame-ui-tabslayoutnpm

dolyame-ui-tabslayout is a confirmed malicious npm package (MAL-2026-13602) 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-tabslayout (npm)

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

What this malware does

On require of the package, index.js loads lib/telemetry.js and polyfill.js, both of which contain dropper logic that selects an OS-specific path, fetches a binary from one of three obfuscated Cloudflare Workers URLs (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev), with a base64-over-DNS-TXT fallback from *.dl.wel1.ru, writes the payload to a temp path under cover names such as dotnet_diag.exe or.cache_, chmods it 0755, and spawns it detached via /bin/sh -c or cmd. Destination hostnames and dangerous API references are assembled at runtime by string-splitting concatenation (e.g. ['oob-worker.cf102-baf','.worke','rs.dev'].join(''), require('child_' + 'process'), fs['chmod'+'Sync']) to evade static scanners. The package presents itself as build/deployment tooling and wraps the dropper inside a fake Sentry-style analytics SDK.

Malicious versions

1 flagged
35.8.1

Indicators of compromise (SHA-256)

eb9bd9546be2ed0456e30701775450a1ee33b0caf58387ba91db7018f7d70bcd

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-tabslayout (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-tabslayout across your stack and pipelines.

  2. If you installed it — respond

    Remove dolyame-ui-tabslayout 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-tabslayout 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-tabslayout 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-tabslayout 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-016983

References

Credits

  • Amazon Inspector · finder

Detect & block this

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