Which versions of bunxler are malicious?

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

How do I remediate bunxler if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunxler (version 1.0.2501).

Malicious package

bunxlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunxler (RubyGems)

MAL-2026-17130

Immediate action

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

gem uninstall bunxler

Malicious versions

1 flagged

1.0.2501

Indicators of compromise (SHA-256)

595a1813d11ca89bf8c395dce0791c7fd71763ba84ea74c55a6d4420e5c2894c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07819

Credits

ReversingLabs · finder

Detect & block this

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