Which versions of bundlefo are malicious?

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

How do I remediate bundlefo if I installed it?

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

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

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

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

Malicious package

bundlefoRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlefo (RubyGems)

MAL-2026-16949

Immediate action

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

gem uninstall bundlefo

Malicious versions

2 flagged

1.0.01.0.99406

Indicators of compromise (SHA-256)

cf83534f8e83c458029e6da388a57aa55b9329a69aa04502f6e6c7d3cce63c29

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07635

Credits

ReversingLabs · finder

Detect & block this

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