Which versions of bunldeo are malicious?

The following RubyGems versions of bunldeo are flagged malicious: 1.0.99624. Treat any of these as compromised.

How do I remediate bunldeo if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldeo (version 1.0.99624).

Malicious package

bunldeoRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldeo (RubyGems)

MAL-2026-17054

Immediate action

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

gem uninstall bunldeo

Malicious versions

1 flagged

1.0.99624

Indicators of compromise (SHA-256)

24e9736bbe69c8f61de42e86a54a14dbac33bfbb8f56ca0ce9e15ec4d6da4bde

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07740

Credits

ReversingLabs · finder

Detect & block this

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