beaver-ui-form-objectnpm
beaver-ui-form-object is a confirmed malicious npm package (MAL-2026-12145) that steals credentials and exfiltrates sensitive data (malicious versions 12.1.7, 34.7.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in beaver-ui-form-object (npm)
What this malware does
On require of beaver-ui-form-object, index.js loads helpers.js which auto-runs a setup routine that selects a platform-specific asset, downloads a binary over HTTPS from rotating Cloudflare Workers hosts whose names are reassembled at runtime from split string arrays (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT fallback channel resolving through sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmodded 0755, and spawned detached via /bin/sh -c or cmd. Hostnames and module identifiers are reconstructed via Array.join to defeat static string scanning, stderr is suppressed by a no-op logger, and filename tokens are randomized. The delivered executable is opaque and its behavior, publisher, and endpoints have no relation to the package's advertised 'ui form object' purpose.
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-form-object (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-form-object across your stack and pipelines.
If you installed it — respond
beaver-ui-form-object 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-form-object 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-form-object 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-form-object-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.