beaver-ui-popover-cardnpm
beaver-ui-popover-card is a confirmed malicious npm package (MAL-2026-12821) that executes malicious code on install (malicious version 35.4.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in beaver-ui-popover-card (npm)
What this malware does
On require('beaver-ui-popover-card'), support.js downloads a platform-specific binary from Cloudflare Workers endpoints whose hostnames are assembled at runtime from split string fragments (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT fallback resolver chain across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to a temp path under disguised names (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0o755, and spawned detached via /bin/sh -c or cmd. No signature or hash verification is performed. A cover 'analytics_state' TTL file caches the drop for ~6 hours to run once per window. A second dropper of the same shape is bundled in lib/telemetry.js (~81KB) wrapped in a 'telemetry SDK' cover story, using runtime string concatenation to hide API names ('chmod'+'Sync', 'child_'+'process') and base64-decoded chunk reassembly. Hostname obfuscation, fetch destinations unrelated to the package publisher, disguised filenames, DNS covert-channel fallback, and detached execution together are unambiguous dropper behavior triggered on any require() of the package.
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-popover-card (version 35.4.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging beaver-ui-popover-card across your stack and pipelines.
If you installed it — respond
Remove beaver-ui-popover-card 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-popover-card 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-popover-card 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-popover-card-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.