beaver-ui-items-with-morenpm
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for beaver-ui-items-with-more (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-items-with-more across your stack and pipelines.
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.
Did it already run?
If beaver-ui-items-with-more 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-items-with-more 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
Campaign
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.