Which versions of bundlir are malicious?

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

How do I remediate bundlir if I installed it?

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

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

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

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

Malicious package

bundlirRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlir (RubyGems)

MAL-2026-16985

Immediate action

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

gem uninstall bundlir

Malicious versions

2 flagged

1.0.01.0.74460

Indicators of compromise (SHA-256)

52026a007683d441adc6bf2778c3fbd2984e3cf4ff888f0c11bec3e079f75383

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07671

Credits

ReversingLabs · finder

Detect & block this

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