Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malicious code in beaver-ui-popover-marker (npm)

beaver-ui-popover-marker, an npm package masquerading as a React UI component, contains malicious code that downloads and executes platform-specific binaries from obfuscated Cloudflare Workers endpoints on require(), granting full host code execution.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system installing or requiring beaver-ui-popover-marker; full host code execution on installation.
Ecosystems
Attack vectors
Affected entities
  • beaver-ui-popover-markernpm package advertised as React UI popover component

The npm package beaver-ui-popover-marker contains malicious code that executes on require(). The package's index.js loads vendor.js, which initiates a bootstrap routine that downloads platform-specific binaries from obfuscated Cloudflare Workers hosts (oob-worker.cf*.workers.dev, with domains reassembled at runtime). The downloaded binary is written as a hidden file to /var/tmp or Windows Temp with a decoy name (.cache or dotnet_diag_.exe), given execute permissions (0755), and spawned detached via /bin/sh or cmd.\n\nThe malicious code includes a DNS TXT fallback mechanism under *.dl.wel1.ru that reassembles base64-encoded payloads when HTTPS fetches fail. A cover-story opt-out gate honors environment variables (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and caches state at /tmp/.analytics_state with a ~5-hour TTL, masquerading as telemetry suppression to avoid re-execution.\n\nThe package is advertised as a legitimate React UI popover component and has no legitimate reason to fetch and execute native binaries from anonymized workers.dev endpoints at import time. Installation or require() of this package grants full-host code execution to an attacker.\n\nThe incident was identified by the OpenSSF malicious-packages project and reported via GitHub Security Advisory GHSA-xmx8-4qhh-xfr8.

Indicators of compromise

Packages
  • beaver-ui-popover-marker
Domains
  • oob-worker.cf*.workers.dev
  • *.dl.wel1.ru

Remediation

  • Immediately uninstall beaver-ui-popover-marker from all systems and projects
  • Audit npm package.json and lock files for any presence of beaver-ui-popover-marker
  • Assume full host compromise on any system that installed or required this package; perform forensic analysis and remediation
  • Review system logs for suspicious binary execution in /var/tmp, Windows Temp, and related directories
  • Monitor for outbound connections to oob-worker.cf*.workers.dev and *.dl.wel1.ru domains
  • Use npm audit to identify and remove the package from dependency trees
  • Consider using npm package signing and verification tools to prevent installation of malicious packages

Sources

  1. GitHub Advisory GHSA-xmx8-4qhh-xfr8 · GitHub Advisory Database

Cite this entry

"Malicious code in beaver-ui-popover-marker (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-beaver-ui-popover-marker-npm-nomq5v

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. activecritical

    Malware in eslint-generate-prerelease

    Malware was discovered in the npm package eslint-generate-prerelease. Systems with this package installed or running should be considered fully compromised.

    npmCompromised package
  2. activecritical

    Malware in celonix-otp-react

    Malware discovered in the npm package celonix-otp-react. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  3. containedcritical

    Malware in resolve-audit

    The npm package resolve-audit was compromised and distributed with malware. Any system with the package installed or running should be considered fully compromised and all secrets/keys rotated immediately from a different machine.

    npmCompromised package
  4. resolvedcritical

    Malware in alphazone

    The npm package alphazone contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.

    npmCompromised package