Which versions of brusndler are malicious?

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

How do I remediate brusndler if I installed it?

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

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

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

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

Malicious package

brusndlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in brusndler (RubyGems)

MAL-2026-16757

Immediate action

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

gem uninstall brusndler

Malicious versions

2 flagged

1.0.01.0.98237

Indicators of compromise (SHA-256)

7a8e550a730236b40f460d79bb6ce61b43b8f47237c3db5921d2db51dedcc723

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07442

Credits

ReversingLabs · finder

Detect & block this

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