Which versions of bunldier are malicious?

The following RubyGems versions of bunldier are flagged malicious: 1.0.35358. Treat any of these as compromised.

How do I remediate bunldier if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldier (version 1.0.35358).

Malicious package

bunldierRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldier (RubyGems)

MAL-2026-17070

Immediate action

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

gem uninstall bunldier

Malicious versions

1 flagged

1.0.35358

Indicators of compromise (SHA-256)

507b68578a50268ba6eb325f1e492d6d4f3d5f2ba9608a3813cd0b62be144509

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07756

Credits

ReversingLabs · finder

Detect & block this

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