Which versions of bujlder are malicious?

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

How do I remediate bujlder if I installed it?

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

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

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

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

Malicious package

bujlderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bujlder (RubyGems)

MAL-2026-16803

Immediate action

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

gem uninstall bujlder

Malicious versions

2 flagged

1.0.01.0.2736

Indicators of compromise (SHA-256)

faebdaf6c15ed0c51bcfac728c16f427d72cd71a6b162b9a531313efe6ceb524

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07488

Credits

ReversingLabs · finder

Detect & block this

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