CRITICAL npm Malware

Malicious code in beaver-ui-smart-filter (npm)

MAL-2026-12824 · GHSA-6h9w-jgrf-pvjf

Published · Modified

Dependency scanning

Check whether beaver-ui-smart-filter is in your codebase

Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.

Description


__

Source: amazon-inspector (a9aeae07ad8c21acdd73d30a24723d30ef468f03a3412e21ea4bf726f27c2f12)

The package is advertised as a React UI filter component but on require of index.js loads adapter.js, which assembles remote hostnames from split string fragments (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT fallback under dl.wel1.ru, downloads a platform-specific binary via https.get, writes it to /tmp or %TEMP% under a disguised name (dotnet_diag.exe on Windows,.cache_ on Unix), chmods it 0755, and spawns it detached via spawn("/bin/sh",["-c",fp+" &"]) or spawn("cmd",...). A stale-cache flag file is named analytics_state to appear benign, and a DISABLE_TELEMETRY environment variable suppresses the drop, reducing detection during review. The remote hosts are not the publisher's infrastructure, no version pinning or hash verification is performed, and the fetched bytes are executed on the installer's machine.

Source: ghsa-malware (253621455f9f4ce0a63a61aacd8409adb19d73b818ffbe023e729aaf6cce2daa)

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.

Ready to move

Start Securing

Free, no credit card | First findings in minutes