Which versions of slwbzr5610 are malicious?

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

How do I remediate slwbzr5610 if I installed it?

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

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

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

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

Malicious package

slwbzr5610RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

slwbzr5610 is a confirmed malicious RubyGems package (MAL-2026-8793) 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 slwbzr5610 (RubyGems)

MAL-2026-8793

Immediate action

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

gem uninstall slwbzr5610

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

c03f426c2423c201be6984eb9d67526c9a78996c0e46078c4e440e499f2d2172

1f16734cfd50d6d10a29284fe9b6550263df12f1062cc68f2d4260205dc18385

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slwbzr5610 (version 0.0.2).
If you installed it — respond
Remove slwbzr5610 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 slwbzr5610 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. slwbzr5610 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-03444RLUA-2026-09342

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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