dolyame-ui-collapseblocknpm
dolyame-ui-collapseblock is a confirmed malicious npm package (MAL-2026-13559) that steals credentials and exfiltrates sensitive data (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-collapseblock (npm)
What this malware does
On require(), shim.js fetches an OS/architecture-specific native binary from hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) whose hostnames are reconstructed at runtime via array-join to evade static inspection. The payload is written to /tmp or %TEMP% under a disguised name (.cache<rand> on Unix, dotnet_diag_<rand>.exe on Windows), chmodded 0755, and spawned detached via /bin/sh -c or cmd. If HTTPS fetches fail, the loader falls back to a DNS-TXT covert channel under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, retrieving a chunk count from c.<domain> and reassembling a base64-encoded binary from sequentially-numbered subdomain TXT records. index.js requires _shim on load, so importing the package auto-executes the fetched attacker-controlled native binary with no version pinning, no hash or signature verification, and destinations unrelated to the package's stated purpose. A 21028-second cache stamp gates repeats and undocumented environment variables provide an operator opt-out, both consistent with hostile dropper tradecraft rather than legitimate functionality.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-collapseblock (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-collapseblock across your stack and pipelines.
If you installed it — respond
dolyame-ui-collapseblock 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-collapseblock 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-collapseblock 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-collapseblock-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.