Which versions of bunxuer are malicious?

The following RubyGems versions of bunxuer are flagged malicious: 1.0.33345. Treat any of these as compromised.

How do I remediate bunxuer if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunxuer (version 1.0.33345).

Malicious package

bunxuerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunxuer (RubyGems)

MAL-2026-17140

Immediate action

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

gem uninstall bunxuer

Malicious versions

1 flagged

1.0.33345

Indicators of compromise (SHA-256)

87ce59c45090b01241af55cc1f533acb1bf9a8f94a274e1f19f840d2f9b9d580

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07829

Credits

ReversingLabs · finder

Detect & block this

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