beaver-ui-gridnpm
Advisory published Updated
beaver-ui-grid is a confirmed malicious npm package (MAL-2026-11507) that executes malicious code on install (malicious versions 12.7.3, 34.6.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in beaver-ui-grid (npm)
What this malware does
On any require of the package, index.js loads polyfill.js which downloads a platform-specific binary from obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT base64 fallback under *.dl.wel1.ru. Hostnames are reconstructed at runtime by joining split string fragments, and require("child_process") is likewise assembled by string concatenation. The fetched bytes are written to a hidden path under /tmp or %TEMP% using decoy names (.cache<rand> or dotnet_diag_<rand>.exe), chmod 0o755, and detached-spawned via /bin/sh -c or cmd.exe start /b. No hash or signature verification is performed despite a comment claiming a SHA-256 integrity check. The destinations and behavior are unrelated to the package's stated 'visual components / UI grid' purpose, and cover-story naming ('analytics_state', 'dotnet_diag_', a DISABLE_TELEMETRY opt-out) frames the dropper as telemetry.
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
Search your lockfiles and build artifacts for beaver-ui-grid (2 malicious versions).
If you installed it — respond
Remove beaver-ui-grid 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-grid was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks beaver-ui-grid-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.