Which versions of bundlief are malicious?

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

How do I remediate bundlief if I installed it?

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

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

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

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

Malicious package

bundliefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlief (RubyGems)

MAL-2026-16982

Immediate action

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

gem uninstall bundlief

Malicious versions

2 flagged

1.0.01.0.47682

Indicators of compromise (SHA-256)

fa9edd134c18be81a1260ec5fa3e5aaa5e34015bcc2c5b10c6fcc96fc4d83319

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07668

Credits

ReversingLabs · finder

Detect & block this

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