Which versions of bundlefa are malicious?

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

How do I remediate bundlefa if I installed it?

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

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

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

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

Malicious package

bundlefaRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlefa (RubyGems)

MAL-2026-16943

Immediate action

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

gem uninstall bundlefa

Malicious versions

2 flagged

1.0.01.0.70960

Indicators of compromise (SHA-256)

ac9527f1a63e500fd60529724f587353c0dc28252efd5841290ebcfde2a26a0f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07629

Credits

ReversingLabs · finder

Detect & block this

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