Which versions of br3e6a6270eb are malicious?

The following RubyGems versions of br3e6a6270eb are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate br3e6a6270eb if I installed it?

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

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

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

Search your lockfiles and build artifacts for br3e6a6270eb (version 0.0.1).

Malicious package

br3e6a6270ebRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

br3e6a6270eb is a confirmed malicious RubyGems package (MAL-2026-7551) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in br3e6a6270eb (RubyGems)

MAL-2026-7551

Immediate action

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

gem uninstall br3e6a6270eb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b27e78f3e7ce3900e3d7054601129d41ae87561d5d853e507d6756ce774355d9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02202

Credits

ReversingLabs · finder

Detect & block this

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