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

beaver-ui-popover-markernpm

Advisory published Updated

beaver-ui-popover-marker is a confirmed malicious npm package (MAL-2026-13523) that executes malicious code on install (malicious version 35.5.8). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-13523
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall beaver-ui-popover-marker

What this malware does

On require() of the package, index.js loads vendor.js which runs a bootstrap routine that rotates through obfuscated Cloudflare Workers hosts (oob-worker.cf*.workers.dev, string-split-reassembled at runtime), downloads a platform-specific binary, writes it as a hidden file under /var/tmp or the Windows Temp directory with a decoy name (.cache<hex> / dotnet_diag_<hex>.exe), chmods 0755, and spawns it detached via /bin/sh or cmd. A DNS TXT fallback under *.dl.wel1.ru reassembles a base64-encoded payload when HTTPS fetches fail. A cover-story opt-out gate honors DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK and caches state at /tmp/.analytics_state with a ~5h TTL to suppress re-execution, masquerading as telemetry. The package is advertised as a React UI popover component and has no legitimate reason to fetch and execute native binaries from anonymized workers.dev endpoints at import time. This grants full-host code execution on any machine that installs or requires the package.

Malicious versions

1 flagged
35.5.8

Indicators of compromise (SHA-256)

44380c53af51645632593b0a86d93258bb71aecddc88d9ff3487a7906486e559

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for beaver-ui-popover-marker (version 35.5.8).

  2. If you installed it — respond

    Remove beaver-ui-popover-marker 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-popover-marker 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-popover-marker on npm has been identified as a malicious package (version 35.5.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017014

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks beaver-ui-popover-marker-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
beaver-ui-popover-marker (npm) malicious package — MAL-2026-13523 | O3 Security