Which versions of bniundler are malicious?

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

How do I remediate bniundler if I installed it?

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

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

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

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

Malicious package

bniundlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bniundler (RubyGems)

MAL-2026-16732

Immediate action

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

gem uninstall bniundler

Malicious versions

2 flagged

1.0.01.0.83252

Indicators of compromise (SHA-256)

c542f6fe4b7c5b699124188b66d66acae0b16f5e0cdf79f67b9b5c7eedb9298e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07400

Credits

ReversingLabs · finder

Detect & block this

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