Which versions of bieundler are malicious?

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

How do I remediate bieundler if I installed it?

Remove bieundler 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 bieundler — how do I know if it already compromised me?

If bieundler 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 bieundler part of a known attack campaign?

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

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

Malicious package

bieundlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bieundler (RubyGems)

MAL-2026-16596

Immediate action

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

gem uninstall bieundler

Malicious versions

2 flagged

1.0.01.0.52837

Indicators of compromise (SHA-256)

b6d0fc225e7060e93312e82489795f03bb99eda13bb894f0e1777e94880feaa3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07255

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bieundler-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