Which versions of bondler are malicious?

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

How do I remediate bondler if I installed it?

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

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

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

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

Malicious package

bondlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bondler (RubyGems)

MAL-2026-16745

Immediate action

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

gem uninstall bondler

Malicious versions

2 flagged

1.0.01.0.63698

Indicators of compromise (SHA-256)

24b87cd0e68781bd07d79dba32831d2aec910133cbb71b64421b97d80b463479

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07413

Credits

ReversingLabs · finder

Detect & block this

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