Which versions of baunlder are malicious?

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

How do I remediate baunlder if I installed it?

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

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

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

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

Malicious package

baunlderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in baunlder (RubyGems)

MAL-2026-16569

Immediate action

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

gem uninstall baunlder

Malicious versions

2 flagged

1.0.01.0.78358

Indicators of compromise (SHA-256)

d91aac8be7b5d932265788d8776fb5339dc4a132de29e539683d4840d992c10b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07216

Credits

ReversingLabs · finder

Detect & block this

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