Which versions of bunldser are malicious?

The following RubyGems versions of bunldser are flagged malicious: 1.0.60801. Treat any of these as compromised.

How do I remediate bunldser if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldser (version 1.0.60801).

Malicious package

bunldserRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldser (RubyGems)

MAL-2026-17081

Immediate action

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

gem uninstall bunldser

Malicious versions

1 flagged

1.0.60801

Indicators of compromise (SHA-256)

8436f8cbe235bd3b84642bcf3b42dde06bc3a876290b69dff30a55a5ba2db65a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07767

Credits

ReversingLabs · finder

Detect & block this

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