Which versions of bunndlef are malicious?

The following RubyGems versions of bunndlef are flagged malicious: 1.0.86049. Treat any of these as compromised.

How do I remediate bunndlef if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunndlef (version 1.0.86049).

Malicious package

bunndlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunndlef (RubyGems)

MAL-2026-17103

Immediate action

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

gem uninstall bunndlef

Malicious versions

1 flagged

1.0.86049

Indicators of compromise (SHA-256)

c0050e9363f08789e978dea1c0d165d8120e738b176a9939053b6a310ed234a8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07789

Credits

ReversingLabs · finder

Detect & block this

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