Which versions of bunsdlef are malicious?

The following RubyGems versions of bunsdlef are flagged malicious: 1.0.21638. Treat any of these as compromised.

How do I remediate bunsdlef if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunsdlef (version 1.0.21638).

Malicious package

bunsdlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunsdlef (RubyGems)

MAL-2026-17119

Immediate action

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

gem uninstall bunsdlef

Malicious versions

1 flagged

1.0.21638

Indicators of compromise (SHA-256)

1fc629ba82b64bff1540597420692b2c122b292852b3a1cca38a3bc4bd3cb9eb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07805

Credits

ReversingLabs · finder

Detect & block this

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