Which versions of bundlef-gem are malicious?

The following RubyGems versions of bundlef-gem are flagged malicious: 1.0.21369. Treat any of these as compromised.

How do I remediate bundlef-gem if I installed it?

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

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

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

Search your lockfiles and build artifacts for bundlef-gem (version 1.0.21369).

Malicious package

bundlef-gemRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bundlef-gem is a confirmed malicious RubyGems package (MAL-2026-16939) that executes malicious code on install (malicious version 1.0.21369). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bundlef-gem (RubyGems)

MAL-2026-16939

Immediate action

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

gem uninstall bundlef-gem

Malicious versions

1 flagged

1.0.21369

Indicators of compromise (SHA-256)

4d71cfbf7472c38c637924efaef8580c4704f7c460fdbada1c969ec7ad027362

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07625

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bundlef-gem-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