Which versions of slvbzr137 are malicious?

The following RubyGems versions of slvbzr137 are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate slvbzr137 if I installed it?

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

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

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

Search your lockfiles and build artifacts for slvbzr137 (version 0.0.2).

Malicious package

slvbzr137RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in slvbzr137 (RubyGems)

MAL-2026-8790

Immediate action

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

gem uninstall slvbzr137

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

2363de32e70f7bcee0e8df906db60e9c77bcd66f40ff90688e195619fdf49b38

df9494ac30495e8f1e18a5408623e042630f3438042e79306187d73145715056

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03441RLUA-2026-09339

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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