Which versions of beaver-ui-layout are malicious?

The following npm versions of beaver-ui-layout are flagged malicious: 12.9.6, 34.2.3. Treat any of these as compromised.

How do I remediate beaver-ui-layout if I installed it?

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.

I already installed beaver-ui-layout — how do I know if it already compromised me?

If beaver-ui-layout 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.

Is beaver-ui-layout part of a known attack campaign?

Yes — beaver-ui-layout is associated with the GHSA-w259-8g6c-8ppr, IN-MAL-2026-011006, IN-MAL-2026-011005 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find beaver-ui-layout across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for beaver-ui-layout (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-layout across your stack and pipelines.

Malicious package

beaver-ui-layoutnpm

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)

MAL-2026-11510

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall beaver-ui-layout

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

2 flagged

12.9.634.2.3

Indicators of compromise (SHA-256)

9811e6fb160c26593c5a92c4d8612648740b6240c20d300daa0bca6784a579e7

48b1d2ab6b78ed58ff344a9e6d6a99fb11267f5b0c974644b052c62bacc4f7f1

465b05640a3068a007c565655d946564a39211eeca92f8637b7c3b4fe9c9dece

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for beaver-ui-layout (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-layout across your stack and pipelines.
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 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-layout 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

No. beaver-ui-layout on npm has been identified as a malicious package (versions 12.9.6, 34.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w259-8g6c-8pprIN-MAL-2026-011006IN-MAL-2026-011005

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database