Which versions of bundleor are malicious?

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

How do I remediate bundleor if I installed it?

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

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

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

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

Malicious package

bundleorRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundleor (RubyGems)

MAL-2026-16962

Immediate action

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

gem uninstall bundleor

Malicious versions

2 flagged

1.0.01.0.6167

Indicators of compromise (SHA-256)

e0850259248d98a44ca0b66398e4c376418f7d888d7216cf553c10966f37ebda

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07648

Credits

ReversingLabs · finder

Detect & block this

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