Which versions of bunlde are malicious?

The following RubyGems versions of bunlde are flagged malicious: 1.0.43264. Treat any of these as compromised.

How do I remediate bunlde if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunlde (version 1.0.43264).

Malicious package

bunldeRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunlde (RubyGems)

MAL-2026-17043

Immediate action

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

gem uninstall bunlde

Malicious versions

1 flagged

1.0.43264

Indicators of compromise (SHA-256)

bb4f38a4acf8a7e6c707fd9bb5d6ac7ac86540e4f82697a452eb59f6e369ab0b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07729

Credits

ReversingLabs · finder

Detect & block this

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