Which versions of bnundler are malicious?

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

How do I remediate bnundler if I installed it?

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

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

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

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

Malicious package

bnundlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bnundler (RubyGems)

MAL-2026-16739

Immediate action

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

gem uninstall bnundler

Malicious versions

2 flagged

1.0.01.0.81828

Indicators of compromise (SHA-256)

0d99e1d3fd114a7653499111287bae048874ef285183c460365f5c2840fc78aa

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07407

Credits

ReversingLabs · finder

Detect & block this

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