Which versions of bunldsr are malicious?

The following RubyGems versions of bunldsr are flagged malicious: 1.0.98458. Treat any of these as compromised.

How do I remediate bunldsr if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunldsr (version 1.0.98458).

Malicious package

bunldsrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunldsr (RubyGems)

MAL-2026-17082

Immediate action

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

gem uninstall bunldsr

Malicious versions

1 flagged

1.0.98458

Indicators of compromise (SHA-256)

2c77596a8a70b651d006c9500b6edf1efffd333fd46ac8e7f261c1391950edb5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07768

Credits

ReversingLabs · finder

Detect & block this

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