Which versions of bunxlner are malicious?

The following RubyGems versions of bunxlner are flagged malicious: 1.0.83014. Treat any of these as compromised.

How do I remediate bunxlner if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunxlner (version 1.0.83014).

Malicious package

bunxlnerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunxlner (RubyGems)

MAL-2026-17136

Immediate action

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

gem uninstall bunxlner

Malicious versions

1 flagged

1.0.83014

Indicators of compromise (SHA-256)

dc2853061d7fc3fe56aa0ad53c5a55542d7a3922cf994db08f9a4602385d375c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07825

Credits

ReversingLabs · finder

Detect & block this

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