Which versions of bunxlerl are malicious?

The following RubyGems versions of bunxlerl are flagged malicious: 1.0.49186. Treat any of these as compromised.

How do I remediate bunxlerl if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunxlerl (version 1.0.49186).

Malicious package

bunxlerlRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunxlerl (RubyGems)

MAL-2026-17132

Immediate action

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

gem uninstall bunxlerl

Malicious versions

1 flagged

1.0.49186

Indicators of compromise (SHA-256)

df8bf446a49008604333bce1548f9527eb8343b7230657b900031f923c0c7652

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07821

Credits

ReversingLabs · finder

Detect & block this

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