Which versions of dolyame-ui-tabs are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-tabsnpm

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

Malicious code in dolyame-ui-tabs (npm)

MAL-2026-13190

Immediate action

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

npm uninstall dolyame-ui-tabs

What this malware does

index.js requires./support, whose top-level run() fetches a platform-specific binary from obfuscated Cloudflare Workers subdomains (reconstructed via array.join() such as ['oob-worker.cf102-baf.','worker','s.','dev']) with a DNS-TXT chunked base64 fallback channel served from *.dl.wel1.ru resolver hosts (e.g. ['sd','k.dl.wel','1.','ru'].join('')). The fetched bytes are written to /tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755'd on POSIX, and spawned detached via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}).unref(). Execution fires on require() of the package, giving arbitrary remote code execution on the installer's host at library-load time. The package is advertised as a React components/tabs library and has no legitimate need for a native binary or DNS-TXT payload channel. lib/telemetry.js contains a structurally identical dormant dropper (HTTPS + DNS discovery, chunk decoding, chmod 755, /bin/sh spawn) that is not reached from the current entry point but ships in the tarball. Hostname reconstruction, disguised drop filenames, and telemetry-styled opt-out env vars indicate deliberate evasion.

Malicious versions

1 flagged

35.3.2

Indicators of compromise (SHA-256)

4beccb0ba046e54873e7d6af1d2023eb5f01a0eab4ed5abe336de2e3e3a74993

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

Campaign

IN-MAL-2026-015585

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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