Which versions of slg99185 are malicious?

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

How do I remediate slg99185 if I installed it?

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

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

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

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

Malicious package

slg99185RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8637

Immediate action

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

gem uninstall slg99185

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

4f33fa58d6b6411b0d7c5a781ff9d899bc98c3a2ff4d790d0195a69e7666ba9a

80eccf91610baceef8a12a7ad66372eaa91c72418f06ce5c09d8b354bfd36eac

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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