Which versions of bundleif are malicious?

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

How do I remediate bundleif if I installed it?

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

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

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

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

Malicious package

bundleifRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundleif (RubyGems)

MAL-2026-16954

Immediate action

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

gem uninstall bundleif

Malicious versions

2 flagged

1.0.01.0.19460

Indicators of compromise (SHA-256)

399f1c7a9982c52752a299af65dfa71aa40b649e6b67c266500e58688f887609

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07640

Credits

ReversingLabs · finder

Detect & block this

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