Which versions of bunxlser are malicious?

The following RubyGems versions of bunxlser are flagged malicious: 1.0.33883. Treat any of these as compromised.

How do I remediate bunxlser if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunxlser (version 1.0.33883).

Malicious package

bunxlserRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunxlser (RubyGems)

MAL-2026-17139

Immediate action

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

gem uninstall bunxlser

Malicious versions

1 flagged

1.0.33883

Indicators of compromise (SHA-256)

b4bb4c8079382bc592d74e2361f1c0d7ac0ef2670d0a67d5f8f3ce3a5b24070c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07828

Credits

ReversingLabs · finder

Detect & block this

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