beaver-ui-smart-filternpm
beaver-ui-smart-filter is a confirmed malicious npm package (MAL-2026-12824) that steals credentials and exfiltrates sensitive data (malicious version 35.1.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in beaver-ui-smart-filter (npm)
What this malware does
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<hex>.exe on Windows,.cache_<hex> 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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for beaver-ui-smart-filter (version 35.1.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging beaver-ui-smart-filter across your stack and pipelines.
If you installed it — respond
beaver-ui-smart-filter is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If beaver-ui-smart-filter 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-smart-filter 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-smart-filter-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.