beaver-ui-icon-lock @34.8.3

Summary

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.

Source: amazon-inspector (dc953ba45a243565fdc2ac41c733bfe5e4d09e9b9362325d2f670b39d1f84618)