Which versions of bunxlenr are malicious?

The following RubyGems versions of bunxlenr are flagged malicious: 1.0.49740. Treat any of these as compromised.

How do I remediate bunxlenr if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunxlenr (version 1.0.49740).

Malicious package

bunxlenrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunxlenr (RubyGems)

MAL-2026-17129

Immediate action

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

gem uninstall bunxlenr

Malicious versions

1 flagged

1.0.49740

Indicators of compromise (SHA-256)

193a2a287f9c4fc7d7a37477cdef0c07625a5c69e296bf42f58e3a67f7d7ef54

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07818

Credits

ReversingLabs · finder

Detect & block this

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