dolyame-ui-tabsblocknpm
dolyame-ui-tabsblock is a confirmed malicious npm package (MAL-2026-13512) that typosquats a legitimate package to trick installs (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-tabsblock (npm)
What this malware does
On require, index.js loads./_compat and./lib/telemetry, both of which reconstruct hostnames at runtime from string fragments (e.g. ["oob-worker.c","f102-baf",".wor","kers",".dev"].join("")) and fetch an opaque platform-specific binary from Cloudflare Workers subdomains oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, and oob-worker.cf101-adf.workers.dev. The bytes are written to /tmp or the Windows temp directory under randomized names such as.cache_XX or dotnet_diag_XX.exe, made executable via fs["chmod"+"Sync"](path, 0o755), and launched detached with cp.spawn("/bin/sh", ["-c", filePath+" &"], {detached:true}).unref(). A time-gated flag in /tmp suppresses re-run within roughly six hours. If HTTPS delivery fails, _compat.js falls back to dns.resolveTxt against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru: it reads a counter TXT record at c.<domain>, then batches queries for numbered subdomains, concatenates the TXT contents, and base64-decodes the result into the executable payload. lib/telemetry.js contains a parallel fetch->write->chmod 755->spawn path camouflaged as a Sentry-lookalike "apm.node" SDK. child_process, chmodSync, and hostname API names are split-string obfuscated to evade static scanners. The package name mimics a Russian BNPL brand while its actual behavior is retrieving and executing attacker-controlled native code on every import.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-tabsblock (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-tabsblock across your stack and pipelines.
If you installed it — respond
dolyame-ui-tabsblock is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-tabsblock, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If dolyame-ui-tabsblock 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-tabsblock 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks dolyame-ui-tabsblock-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.