Which versions of bunnxler are malicious?

The following RubyGems versions of bunnxler are flagged malicious: 1.0.31113. Treat any of these as compromised.

How do I remediate bunnxler if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunnxler (version 1.0.31113).

Malicious package

bunnxlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunnxler (RubyGems)

MAL-2026-17106

Immediate action

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

gem uninstall bunnxler

Malicious versions

1 flagged

1.0.31113

Indicators of compromise (SHA-256)

acf199c2d41d4f8a375dbdd1ab9eac38949fcf18b43224a1f2f6b86023cd8c02

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07792

Credits

ReversingLabs · finder

Detect & block this

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