Which versions of buinlder are malicious?

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

How do I remediate buinlder if I installed it?

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

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

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

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

Malicious package

buinlderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in buinlder (RubyGems)

MAL-2026-16798

Immediate action

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

gem uninstall buinlder

Malicious versions

2 flagged

1.0.01.0.97187

Indicators of compromise (SHA-256)

52db0e7cc6b64bdc82ed2afc4d7b4a307d3eeaf83e76cfd3a7b7224ea54711dc

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07483

Credits

ReversingLabs · finder

Detect & block this

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