Which versions of bundlfe are malicious?

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

How do I remediate bundlfe if I installed it?

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

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

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

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

Malicious package

bundlfeRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlfe (RubyGems)

MAL-2026-16981

Immediate action

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

gem uninstall bundlfe

Malicious versions

2 flagged

1.0.01.0.91837

Indicators of compromise (SHA-256)

3cfcb9aeacc492fc0b0517885fd0ce9f7d270ddda2cbe8c593a7ee4ec4b4a862

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07667

Credits

ReversingLabs · finder

Detect & block this

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