Which versions of bundlner are malicious?

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

How do I remediate bundlner if I installed it?

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

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

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

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

Malicious package

bundlnerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundlner (RubyGems)

MAL-2026-16989

Immediate action

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

gem uninstall bundlner

Malicious versions

2 flagged

1.0.01.0.66161

Indicators of compromise (SHA-256)

97a7a8bea899dd68936430c446dc05c8953ac20162044355c04cdc042e12e0a2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07675

Credits

ReversingLabs · finder

Detect & block this

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