dolyame-ui-pageheadernpm
dolyame-ui-pageheader is a confirmed malicious npm package (MAL-2026-13592) 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-pageheader (npm)
What this malware does
The package advertises itself as 'Common TypeScript definitions' but its main entry (index.js) unconditionally requires./bridge on load. bridge.js selects a platform-specific payload path, fetches an opaque binary over HTTPS from one of four Cloudflare workers.dev hosts (oob-worker.cf100-416.workers.dev, cf102-baf, cf101-adf, cf103-070.workers.dev) with a DNS-TXT chunked base64 fallback via *.dl.wel1.ru, writes it to /tmp or %TEMP% under disguised names such as dotnet_diag<hex>.exe or.cache<hex>, chmods 0755, and spawns it detached via spawn('/bin/sh', ['-c', filePath + ' &']) or the Windows equivalent — with no hash or signature verification. Endpoint hostnames and the 'child_process' API name are assembled from split string arrays (['oob-worker.cf100-4','16.wo','rkers.dev'].join(''); require('child_'+'process')) to defeat static string scans. lib/telemetry.js carries the same fetch/write/chmod/detached-spawn primitives as a redundant load-time execution channel. Installing or requiring this package grants full-host remote code execution to the operator of the workers.dev endpoints.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-pageheader (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-pageheader across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-pageheader 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.
Did it already run?
If dolyame-ui-pageheader 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-pageheader 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-pageheader-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.