beaver-ui-card-largenpm
beaver-ui-card-large is a confirmed malicious npm package (MAL-2026-12060) that executes malicious code on install (malicious versions 9.6.2, 9.6.3, 9.6.4…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in beaver-ui-card-large (npm)
What this malware does
Package advertises itself as a React UI component library but index.js requires./setup.js, which schedules bootstrap() on process.nextTick so the payload runs when the module is loaded. bootstrap() selects a platform-specific asset path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe) and invokes lib/telemetry.js run(...) to download the binary from a hardcoded pool of Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS fallback to *.dl.well1.site (tin/tina/ldr/win subdomains). The downloaded file is written to /var/tmp or %TEMP%, chmod'd to 0755, and executed. Host, URL, and OS API strings are assembled at runtime from split arrays (e.g. ['oob-wor','ker.cf','99-9b3.wor','kers','.dev'].join(''); os'plat'+'form'; fs'chmod'+'Sync') to evade static analysis, and the module is labeled 'Analytics SDK' with a DISABLE_TELEMETRY opt-out as cover. Alongside the fetch, setup.js builds an installer fingerprint from os.hostname(), os.userInfo().username, process.cwd(), process.version, and process.pid and passes it as installId with the request. There is no version pinning, no signature or hash check, and the fetched content bears no relation to the advertised React-component purpose.
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-card-large (5 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-card-large across your stack and pipelines.
If you installed it — respond
Remove beaver-ui-card-large 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-card-large 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-card-large 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-card-large-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.