Which versions of bundlif are malicious?

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

How do I remediate bundlif if I installed it?

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

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

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

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

Malicious package

bundlifRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlif (RubyGems)

MAL-2026-16984

Immediate action

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

gem uninstall bundlif

Malicious versions

2 flagged

1.0.01.0.2227

Indicators of compromise (SHA-256)

f8045e283a52ac875f6eea911c141dda7d439aea515cd2e55183925d7f0a033f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07670

Credits

ReversingLabs · finder

Detect & block this

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