Which versions of bundier are malicious?

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

How do I remediate bundier if I installed it?

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

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

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

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

Malicious package

bundierRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundier (RubyGems)

MAL-2026-16919

Immediate action

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

gem uninstall bundier

Malicious versions

2 flagged

1.0.01.0.14195

Indicators of compromise (SHA-256)

9db48e18d42f986d63b11b5bf504792609564d9c71843a7c7c3a1d51e058cd21

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07605

Credits

ReversingLabs · finder

Detect & block this

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