NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

dolyame-ui-tagnpm

Advisory published Updated

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

Malicious code in dolyame-ui-tag (npm)

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

What this malware does

On require of the package, index.js loads./ext, which downloads a platform-specific binary from Cloudflare Workers hosts assembled at runtime from split string fragments (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS-TXT covert-channel fallback via subdomains of dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The fetched binary is written under a decoy name (dotnet_diag.exe on Windows,.cache_ on Unix) to %TEMP%/ /tmp, chmodded 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}) or cp.spawn('cmd.exe', ['/c','start','/b',fp]). A second dropper of the same shape is present in lib/telemetry.js and uses split identifiers (require('child_' + 'process'), fs['chmod' + 'Sync']) to evade static analysis. Hostname obfuscation, DNS-TXT fallback for HTTPS-blocked environments, decoy filenames, detached execution, and a bundled backup dropper are consistent with a supply-chain attack delivering attacker-controlled code to installer machines on any install or require of the package.

Malicious versions

1 flagged
35.9.9

Indicators of compromise (SHA-256)

62b169f56912efe4d5ade33f60cbc3f4b220ac0c447ff5821d8cd96635a1a67c

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for dolyame-ui-tag (version 35.9.9).

  2. If you installed it — respond

    Remove dolyame-ui-tag 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-tag was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dolyame-ui-tag on npm has been identified as a malicious package (version 35.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015587

References

Credits

  • Amazon Inspector · finder

Detect & block this

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