Malicious code in beaver-ui-card-large (npm)
The npm package beaver-ui-card-large contained malicious code that downloads and executes platform-specific binaries from attacker-controlled Cloudflare Workers hosts and DNS fallback domains upon module load. The package was disguised as a React UI component library with fake telemetry functionality.
- Disclosed
- Last updated
- Blast radius
- Any developer or application that installed beaver-ui-card-large from npm; arbitrary code execution on developer machines and in production environments.
- Ecosystems
- Attack vectors
- Affected entities
- beaver-ui-card-largenpm package containing malicious code in index.js and setup.js
The npm package beaver-ui-card-large was found to contain malicious code that executes automatically when the module is loaded. The package's index.js file requires setup.js, which schedules a bootstrap() function to run on process.nextTick, ensuring the payload executes during module initialization.
The bootstrap() function selects a platform-specific binary path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe) and uses lib/telemetry.js to download the binary from a hardcoded pool of attacker-controlled 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 DNS fallback to *.dl.well1.site subdomains (tin, tina, ldr, win). The downloaded binary is written to /var/tmp or %TEMP%, made executable (chmod 0755), and executed immediately.
To evade static analysis, the malicious code assembles host names, URLs, and OS API calls at runtime using split arrays and string concatenation (e.g., ['oob-wor','ker.cf','99-9b3.wor','kers','.dev'].join('')). The package falsely advertises itself as an Analytics SDK with a DISABLE_TELEMETRY environment variable as cover. During the fetch, setup.js builds an installer fingerprint from os.hostname(), os.userInfo().username, process.cwd(), process.version, and process.pid, passing this as installId with the request. There is no version pinning, signature verification, or hash validation of the downloaded content.
Indicators of compromise
- Packages
- beaver-ui-card-large
- Domains
- 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
- tin.dl.well1.site
- tina.dl.well1.site
- ldr.dl.well1.site
- win.dl.well1.site
Remediation
- Immediately uninstall beaver-ui-card-large from all projects and development environments
- Audit npm package.json and lock files for any presence of beaver-ui-card-large
- Review process execution logs and network traffic for connections to oob-worker.cf*.workers.dev or *.dl.well1.site domains
- Assume any machine that installed this package may be compromised; consider full system audit and potential reimaging
- Check for unexpected binaries in /var/tmp or %TEMP% directories on affected systems
- Update all dependencies and perform a full security audit of the supply chain
- Monitor for indicators of compromise from any binaries that may have been downloaded and executed
Sources
- GitHub Advisory GHSA-v8v9-qm2p-x684 · GitHub Advisory Database
Cite this entry
"Malicious code in beaver-ui-card-large (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-beaver-ui-card-large-npm-m5vnws
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in santana-baileys (npm)
Malicious code discovered in santana-baileys npm package that covertly relays WhatsApp messaging data to an attacker-controlled endpoint (https://fiora.nixel.my.id/) via obfuscated character-code reconstruction in the message-send code path.
npmCompromised package - resolvedcritical
Malicious code in elephant-tusk-runner (npm)
The npm package elephant-tusk-runner contained malicious code that exposed a remote shell and remote code execution surface via an unauthenticated Express + WebSocket server binding to 0.0.0.0:4201 with fully open CORS. Any peer able to reach the port could execute arbitrary commands on the host.
npmCompromised package - resolvedcritical
Malicious code in @cats-cdf/browser-metrics-meter (npm)
The npm package @cats-cdf/browser-metrics-meter contained malicious code in its preinstall lifecycle script that exfiltrated system reconnaissance data (username, hostname, public IP) to an OAST collector domain. The package executed this behavior unconditionally on installation without consent or documented purpose.
npmCompromised package - resolvedcritical
Malicious code in @ks-video/kwai-player-web (npm)
The npm package @ks-video/kwai-player-web contained malicious code in its postinstall hook that exfiltrated system reconnaissance data (hostname, username, working directory, network interfaces, environment variable names) over plain HTTP to an unrelated third-party domain. The package has no legitimate relationship to the declared publisher Kwai/@ks-video.
npmCompromised package