NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

beaver-ui-form-objectnpm

Advisory published Updated

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)

MAL-2026-12145
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall beaver-ui-form-object

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

3 flagged
12.1.734.7.535.7.3

Indicators of compromise (SHA-256)

095bc606e3637984699ba5a1c4d342d49fde26124f3b5ce48c07d52b912c9f6a
2f7046f5b562c036abf7df81fad298df022f7442790baab48bedaeac92b558b3
b5b91edd276d95174766d639bab6981de8e07b4261e57668fc61f8e7dd96cc1e
dcb6256c0a6b54da5f083f0ebe7609d6b1d6b4a7b517c6008486e9050583d8bf

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for beaver-ui-form-object (3 malicious versions).

  2. 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.

  3. Did it already run?

    If beaver-ui-form-object was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. beaver-ui-form-object on npm has been identified as a malicious package (versions 12.1.7, 34.7.5, 35.7.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014457IN-MAL-2026-014460IN-MAL-2026-015567GHSA-7f2m-rv2g-c7q2

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.

Explore

beaver-ui-form-object (npm) malicious package — MAL-2026-12145 | O3 Security