beaver-ui-form-objectnpm
beaver-ui-form-object is a confirmed malicious npm package (MAL-2026-12145) that executes malicious code on install (malicious versions 12.1.7, 34.7.5, 35.7.3). 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 the package, index.js loads _polyfill.js whose top-level bootstrap() fetches an opaque platform-specific binary over HTTPS from string-fragment-assembled hosts (reconstructing oob-worker.cf101-adf.workers.dev and sdk.dl.wel1.ru, with a DNS-TXT fallback for endpoint discovery), writes it to /var/tmp or %TEMP% under disguised names such as dotnet_diag_<hex>.exe and .cache_<hex>, chmods it 755, and spawns it detached via cp.spawn("/bin/sh", ["-c", fp+" &"], {detached:true}).unref() (with a cmd branch on Windows). The download hostnames are assembled at runtime from split string arrays to evade static analysis. A second bundled module, lib/telemetry.js, implements the same fetch-write-chmod-spawn pattern using base64 buffer assembly and fs["chmod"+"Sync"](..., 0o755). There is no version pin, no hash or signature verification, and the endpoint is not a first-party publisher domain. Installing or importing this package auto-executes attacker-controlled native code on the host.
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.
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-form-object (3 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
Remove beaver-ui-form-object 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-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 malicious outbound activity and severs the channel.