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

beaver-ui-items-with-morenpm

Advisory published Updated

beaver-ui-items-with-more is a confirmed malicious npm package (MAL-2026-11509) that executes malicious code on install (malicious versions 12.2.6, 34.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in beaver-ui-items-with-more (npm)

MAL-2026-11509
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall beaver-ui-items-with-more

What this malware does

The package's declared postinstall (node setup.js) and its main entry index.js (which unconditionally calls require('./setup')) fetch a platform-specific executable from string-fragmented Cloudflare Workers hostnames (reassembled at runtime from arrays via .join(''), e.g. oob-worker.cfNN-XXX.workers.dev) with a DNS-TXT base64 covert-channel fallback under *.dl.well1.site. The downloaded bytes are written to /var/tmp or %TEMP% under a hidden randomized name (.cache_<hex> / dotnet_diag_<hex>.exe), chmod 0755 on Unix, and launched detached via execFile with child.unref(). No hash or signature verification, no pinning, and the destinations are obfuscated to evade static hostname scanning. setup.js also uses child_process including execSync('powershell...'). The behavior fires both on npm install (postinstall) and on require() of the package, giving the operator of the fetched binary full-host code execution on the installer.

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.2.634.1.2

Indicators of compromise (SHA-256)

7bbe189f5c1de0f1dfa82a7b532b58ce8b91852acbba632a941a5f3281aafb4d
6c1daccfac428195187be33025eb0f9094d2196ca643e3eb339e74a24c215ba1
c8d4373a44723e70f9c331d4a0c277a0cbcfc0d2acc4f3af4fbd2449754eb4a8

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for beaver-ui-items-with-more (2 malicious versions).

  2. If you installed it — respond

    Remove beaver-ui-items-with-more 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-items-with-more 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-items-with-more on npm has been identified as a malicious package (versions 12.2.6, 34.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qq8g-w3r7-rqp8IN-MAL-2026-011032IN-MAL-2026-011033

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks beaver-ui-items-with-more-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-items-with-more (npm) malicious package — MAL-2026-11509 | O3 Security