Which versions of bunxlir are malicious?

The following RubyGems versions of bunxlir are flagged malicious: 1.0.4602. Treat any of these as compromised.

How do I remediate bunxlir if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunxlir (version 1.0.4602).

Malicious package

bunxlirRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunxlir (RubyGems)

MAL-2026-17135

Immediate action

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

gem uninstall bunxlir

Malicious versions

1 flagged

1.0.4602

Indicators of compromise (SHA-256)

8029eb95e8e8c90dce8ce3bbdc4e89b86718b1b39905fbcb075ea219235e1c83

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07824

Credits

ReversingLabs · finder

Detect & block this

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