Which versions of bunldner are malicious?

The following RubyGems versions of bunldner are flagged malicious: 1.0.35572. Treat any of these as compromised.

How do I remediate bunldner if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldner (version 1.0.35572).

Malicious package

bunldnerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldner (RubyGems)

MAL-2026-17074

Immediate action

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

gem uninstall bunldner

Malicious versions

1 flagged

1.0.35572

Indicators of compromise (SHA-256)

4294c6fd34511fa37d37a7b126a74bebc4bfd5c9a4c75f72ff86ea41b6654247

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07760

Credits

ReversingLabs · finder

Detect & block this

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