Which versions of beiundler are malicious?

The following RubyGems versions of beiundler are flagged malicious: 1.0.0, 1.0.2495. Treat any of these as compromised.

How do I remediate beiundler if I installed it?

Remove beiundler 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.

I already installed beiundler — how do I know if it already compromised me?

If beiundler 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.

Is beiundler part of a known attack campaign?

Yes — beiundler is associated with the RLMA-2026-07229 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 beiundler across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for beiundler (2 malicious versions).

Malicious package

beiundlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

beiundler is a confirmed malicious RubyGems package (MAL-2026-16577) that executes malicious code on install (malicious versions 1.0.0, 1.0.2495). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in beiundler (RubyGems)

MAL-2026-16577

Immediate action

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

gem uninstall beiundler

Malicious versions

2 flagged

1.0.01.0.2495

Indicators of compromise (SHA-256)

c1779e854356bbabf2ea46d1c5530947d05e3de2047d35b05ed5495af4f781d5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for beiundler (2 malicious versions).
If you installed it — respond
Remove beiundler 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 beiundler 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. beiundler on RubyGems has been identified as a malicious package (versions 1.0.0, 1.0.2495 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-07229

Credits

ReversingLabs · finder

Detect & block this

O3 blocks beiundler-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database