beaver-ui-headernpm
beaver-ui-header is a confirmed malicious npm package (MAL-2026-11508) that executes malicious code on install (malicious versions 12.3.9, 34.6.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in beaver-ui-header (npm)
What this malware does
[email protected] advertises itself as a UI header library but ships a setup.js that runs on npm postinstall and again on require via index.js. It reconstructs network destinations at runtime by joining arrays of substrings (e.g. ['oob-wor','ker.cf','99-9b3.wor','kers','.dev']) to hide Cloudflare Workers hosts of the form oob-worker.cfNN-*.workers.dev, with a DNS-TXT fallback channel that reassembles a base64 payload from numbered TXT records under *.dl.well1.site (c.<domain>, 0.<domain>, 1.<domain>,...). A platform-specific binary is downloaded, staged under /var/tmp or the Windows TEMP directory with a disguised name (dotnet_diag_<tag>.exe on Windows,.cache_<tag> on Unix), chmodded 0755, and launched detached/unref'd via execFile with stdio ignored. Setup.js also invokes execSync('powershell...') on Windows. Variable and env-var names (analytics_state, DISABLE_TELEMETRY, ANALYTICS_OPT_OUT) and the dotnet_diag_ filename frame the flow as telemetry, but the package's stated purpose (UI header component) has no need for platform-specific native binaries, and the destinations are not the publisher's infrastructure. There is no version pin, hash, or signature verification on the downloaded binary.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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 beaver-ui-header (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging beaver-ui-header across your stack and pipelines.
If you installed it — respond
Remove beaver-ui-header 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 beaver-ui-header 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 beaver-ui-header 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 beaver-ui-header-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.