Which versions of bundlur are malicious?

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

How do I remediate bundlur if I installed it?

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

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

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

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

Malicious package

bundlurRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlur (RubyGems)

MAL-2026-17004

Immediate action

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

gem uninstall bundlur

Malicious versions

2 flagged

1.0.01.0.72871

Indicators of compromise (SHA-256)

a8b0bd6010d870f373d87e28688dc1493b14a145a2b505e3a9a31b49b8cf77a0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07690

Credits

ReversingLabs · finder

Detect & block this

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