Which versions of buindlef are malicious?

The following RubyGems versions of buindlef are flagged malicious: 1.0.0, 1.0.81569. Treat any of these as compromised.

How do I remediate buindlef if I installed it?

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

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

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

Search your lockfiles and build artifacts for buindlef (2 malicious versions).

Malicious package

buindlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

buindlef is a confirmed malicious RubyGems package (MAL-2026-16796) that executes malicious code on install (malicious versions 1.0.0, 1.0.81569). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in buindlef (RubyGems)

MAL-2026-16796

Immediate action

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

gem uninstall buindlef

Malicious versions

2 flagged

1.0.01.0.81569

Indicators of compromise (SHA-256)

048626770f570743a1861f9352d5f8466eb51c10d9f0a36d1cf7bb2651634461

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07481

Credits

ReversingLabs · finder

Detect & block this

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