Which versions of bunxler-rb are malicious?

The following RubyGems versions of bunxler-rb are flagged malicious: 1.0.97520. Treat any of these as compromised.

How do I remediate bunxler-rb if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunxler-rb (version 1.0.97520).

Malicious package

bunxler-rbRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bunxler-rb is a confirmed malicious RubyGems package (MAL-2026-17131) that executes malicious code on install (malicious version 1.0.97520). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bunxler-rb (RubyGems)

MAL-2026-17131

Immediate action

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

gem uninstall bunxler-rb

Malicious versions

1 flagged

1.0.97520

Indicators of compromise (SHA-256)

cd9ecdd4a51376a5c4d44dd39b07265702a9919106e695cc9e500a1ac58cf912

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07820

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bunxler-rb-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