Which versions of biujdler are malicious?

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

How do I remediate biujdler if I installed it?

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

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

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

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

Malicious package

biujdlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in biujdler (RubyGems)

MAL-2026-16622

Immediate action

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

gem uninstall biujdler

Malicious versions

2 flagged

1.0.01.0.37645

Indicators of compromise (SHA-256)

ad735500ba80e9ceadb411b885449b909188611e5b178a08e3b47927dc2994a5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07286

Credits

ReversingLabs · finder

Detect & block this

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