beaver-ui-layoutnpm
Advisory published Updated
beaver-ui-layout is a confirmed malicious npm package (MAL-2026-11510) that steals credentials and exfiltrates sensitive data (malicious versions 12.9.6, 34.2.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in beaver-ui-layout (npm)
What this malware does
The package is advertised as a React UI layout library but on require('beaver-ui-layout') loads bridge.js, which reconstructs hostnames from array-joined string fragments to build Cloudflare Workers URLs (oob-worker.cf100/cf101/cf102-*.workers.dev) and a DNS-TXT covert-channel fallback under *.dl.wel1.ru, downloads a platform-specific binary, writes it to /var/tmp or the Windows TEMP directory under disguised names such as dotnet_diag.exe and.cache_, chmods it 0755, and spawns it detached via cp.spawn('/bin/sh', ['-c', fp+' &']) or spawn('cmd',...). A marker file (analytics_state/.analytics_state) is used to gate re-execution, and DISABLE_TELEMETRY/DO_NOT_TRACK environment variables are checked as a cover story. lib/telemetry.js bundles the same dropper primitives (base64 chunk buffer, chmod 755, /bin/sh spawn, require('child_'+'process') split-string obfuscation) as an alternate variant. Importing this package results in arbitrary attacker-controlled code executing on the installer's host.
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
Credential / info stealerFind it
Search your lockfiles and build artifacts for beaver-ui-layout (2 malicious versions).
If you installed it — respond
beaver-ui-layout 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 beaver-ui-layout 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-layout-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.