Which versions of bujdler are malicious?

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

How do I remediate bujdler if I installed it?

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

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

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

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

Malicious package

bujdlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bujdler (RubyGems)

MAL-2026-16802

Immediate action

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

gem uninstall bujdler

Malicious versions

2 flagged

1.0.01.0.63942

Indicators of compromise (SHA-256)

6ee24463f48419f0eabaf1e1a669b80361fd8ef7dab4ce7510e2bd7bbad631b0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07487

Credits

ReversingLabs · finder

Detect & block this

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