NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

beaver-ui-tablenpm

Advisory published Updated

beaver-ui-table is a confirmed malicious npm package (MAL-2026-12828) that executes malicious code on install (malicious version 35.2.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in beaver-ui-table (npm)

MAL-2026-12828
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall beaver-ui-table

What this malware does

The package's main index.js unconditionally requires./setup.js at load time. setup.js selects a platform-specific path, downloads an opaque native binary over HTTPS from one of four Cloudflare Worker subdomains whose hostnames are assembled by joining string-array fragments at runtime (oob-worker.cf99-9b3.workers.dev, cf100-416.workers.dev, cf101-adf.workers.dev, cf102-baf.workers.dev), with a DNS-TXT covert-channel fallback under *.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under disguised names (.cache_<hex>, dotnet_diag_<hex>.exe), chmod 0755'd, and spawned detached via cp.spawn('/bin/sh',['-c',fp+' &'],{detached:true}) or spawn('cmd',...). A rate-limit stamp file (.analytics_state) is written alongside. An unreferenced lib/telemetry.js (~81KB) mirrors the dropper logic (endpoint rotation, DNS discovery, chmod 0755, /bin/sh spawn) as a staged/decoy module. Host obfuscation via.join(''), disguised filenames, anonymous Cloudflare Worker hosting, DNS-TXT fallback, and detached background execution together match the binary-runner dropper pattern; no legitimate native-build or vendor-SDK flow is present.

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

1 flagged
35.2.7

Indicators of compromise (SHA-256)

5eaa4db154b26013412a01287354ef2f0ffb074b9bfd27c6e214fd60ddf4c9be
902f51407b0ac15463a079429c60ae7243e4ad60f6016218523ac7502f58948f

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for beaver-ui-table (version 35.2.7).

  2. If you installed it — respond

    Remove beaver-ui-table 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.

  3. Did it already run?

    If beaver-ui-table 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

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

Campaign

IN-MAL-2026-015548GHSA-c2x3-gq64-h6w5

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks beaver-ui-table-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.

Explore

beaver-ui-table (npm) malicious package — MAL-2026-12828 | O3 Security