Which versions of bnundlef are malicious?

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

How do I remediate bnundlef if I installed it?

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

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

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

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

Malicious package

bnundlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bnundlef (RubyGems)

MAL-2026-16738

Immediate action

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

gem uninstall bnundlef

Malicious versions

2 flagged

1.0.01.0.55050

Indicators of compromise (SHA-256)

c42bb14f1bb8c4a974c7f572294a5e8bfef1901ad0a7bd3aefd5de76ab8a1ef1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07406

Credits

ReversingLabs · finder

Detect & block this

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