Which versions of bunldur are malicious?

The following RubyGems versions of bunldur are flagged malicious: 1.0.63445. Treat any of these as compromised.

How do I remediate bunldur if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldur (version 1.0.63445).

Malicious package

bunldurRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldur (RubyGems)

MAL-2026-17083

Immediate action

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

gem uninstall bunldur

Malicious versions

1 flagged

1.0.63445

Indicators of compromise (SHA-256)

52b98fc2448e785bfffff85d708dbc657dd888e957fa494cc2b78b769874ed86

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07769

Credits

ReversingLabs · finder

Detect & block this

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