beaver-ui-icon-locknpm
beaver-ui-icon-lock is a confirmed malicious npm package (MAL-2026-12147) that executes malicious code on install (malicious versions 12.2.3, 34.8.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in beaver-ui-icon-lock (npm)
What this malware does
The package's postinstall script setup.js selects a platform-specific asset path and fetches an executable from a list of Cloudflare Workers subdomains (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) whose hostnames are reassembled at runtime from split-string arrays such as ["oob-wor","ker.cf","99-9b3.wor","kers",".dev"].join(""). A DNS-TXT-over-.well1.site fallback channel (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site) reconstructs a base64-encoded payload from numbered TXT records (c.<domain> for count, then i.<domain> chunks base64-decoded and concatenated). The fetched bytes are written to /tmp/.cache_<hex> or %TEMP%\dotnet_diag_<hex>.exe, chmod 0o755 on POSIX, and launched with execFile(fp, [], { detached: true, stdio: ["ignore", out, out] }); child.unref() — output redirected to /dev/null and the child detached from the parent. No hash or signature verification is performed and the payload's purpose is unrelated to the package's stated visual-components function. index.js additionally contains try { require("./setup"); } catch (_) {} at the bottom of the entrypoint, so requiring or importing beaver-ui-icon-lock re-runs the same fetch-and-execute chain (gated by a 6-hour stamp file) even when installs use --ignore-scripts. Cloudflare Workers subdomains and DNS-TXT-over-.well1.site are attacker-controlled distribution infrastructure with no relationship to the package's declared publisher or purpose.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for beaver-ui-icon-lock (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging beaver-ui-icon-lock across your stack and pipelines.
If you installed it — respond
Remove beaver-ui-icon-lock 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.
Did it already run?
If beaver-ui-icon-lock 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-icon-lock 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-icon-lock-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.