Which versions of beaver-ui-form are malicious?

The following npm versions of beaver-ui-form are flagged malicious: 12.6.1, 34.9.1. Treat any of these as compromised.

How do I remediate beaver-ui-form if I installed it?

beaver-ui-form establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed beaver-ui-form — how do I know if it already compromised me?

If beaver-ui-form 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.

Is beaver-ui-form part of a known attack campaign?

Yes — beaver-ui-form is associated with the IN-MAL-2026-010978, IN-MAL-2026-014463 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find beaver-ui-form across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for beaver-ui-form (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 across your stack and pipelines.

Malicious package

beaver-ui-formnpm

beaver-ui-form is a confirmed malicious npm package (MAL-2026-11522) that opens a backdoor for remote access (malicious versions 12.6.1, 34.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in beaver-ui-form (npm)

MAL-2026-11522

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall beaver-ui-form

What this malware does

Package advertises itself as a React UI toolkit but on require(), helpers.js runs init() at module load which selects a platform-specific URL, fetches a native binary over HTTPS from obfuscated Cloudflare Workers subdomains (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev), writes it to /tmp under a disguised name (.cache<hex>) on Linux/macOS or to %TEMP% as dotnet_diag_<hex>.exe on Windows, chmods 755, and spawns it detached via /bin/sh -c or cmd.exe (_helpers.js:122-128). C2 hostnames are constructed via array-join string splits to evade static analysis, stderr is suppressed by a no-op wrapper, and DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK environment checks provide a telemetry cover story. If the HTTPS retrieval fails, the code falls back to a DNS-TXT covert channel: it resolves TXT records at c.<sub>.dl.wel1.ru for a chunk count, iterates 0..N.<sub>.dl.wel1.ru TXT records (sdk/ext/pkg/net.dl.wel1.ru), base64-decodes the concatenation into a payload buffer, writes it to disk and executes it. Result is full-host remote code execution on any developer machine or CI runner that installs and requires the package.

Malicious versions

2 flagged

12.6.134.9.1

Indicators of compromise (SHA-256)

c303fcf069e3feb6dfa3d2b8ba7b7b2251c89d796bcf9fcd5d05e44849c64a0d

f730a613c29fd6c66668d4cb7ff46e1f0dc41db9c33af96955df7f2d0b47585c

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for beaver-ui-form (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 across your stack and pipelines.
If you installed it — respond
beaver-ui-form establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If beaver-ui-form 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 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

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

Campaign

IN-MAL-2026-010978IN-MAL-2026-014463

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks beaver-ui-form-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database