beaver-ui-list (npm) · Malicious Code
Affects beaver-ui-listSource GCVE Database
Malicious package : remove beaver-ui-list and rotate any secrets on hosts that installed it.
Data as of 6 Aug 2026, 18:24 UTC
Malicious package
Published to npm · OSV MAL-2026-12817
What to do
Remove beaver-ui-list from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmbeaver-ui-list | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (1f257786868c5d56c3f9f79e674980d07bfad3a42194819837623614554abb77) On require('beaver-ui-list'), index.js loads _ext.js, which selects a payload path based on OS and architecture, downloads a native binary from hardcoded Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS-TXT chunked fallback to *.dl.wel1.ru, writes it to /tmp or %TEMP% under a disguised name (.cache_<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods it 0755, and spawns it detached via /bin/sh or cmd. Host and domain literals are assembled at runtime from split-string arrays joined with.join("") to defeat static inspection, and a.analytics_state marker file plus a check of DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK environment variables provide a telemetry cover story. The package advertises itself as a UI component library; the payload delivery and execution have no relationship to that purpose and grant arbitrary code execution on the installer's host on module load. ## Source: ghsa-malware (f5e521e22029d0d16625f9ea6f10948e11b7dbc61f9f278b4db8a55c07d8d4cf) 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.