Which versions of bunalder are malicious?

The following RubyGems versions of bunalder are flagged malicious: 1.0.0, 1.0.30181. Treat any of these as compromised.

How do I remediate bunalder if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunalder (2 malicious versions).

Malicious package

bunalderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bunalder is a confirmed malicious RubyGems package (MAL-2026-16899) that executes malicious code on install (malicious versions 1.0.0, 1.0.30181). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bunalder (RubyGems)

MAL-2026-16899

Immediate action

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

gem uninstall bunalder

Malicious versions

2 flagged

1.0.01.0.30181

Indicators of compromise (SHA-256)

9d3da75be64f4daf619a4450abf123d05a9b2606ff68c5be651235ae6370f07f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07585

Credits

ReversingLabs · finder

Detect & block this

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