Which versions of slg20883 are malicious?

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

How do I remediate slg20883 if I installed it?

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

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

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

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

Malicious package

slg20883RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8636

Immediate action

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

gem uninstall slg20883

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

abd9d0389f6763e9cdceb562c12a31353ed4d91a87d274e3bb9d664b3f485cd8

c78260931b5e3ba1ce3c9248773d3f16f9e6a5f8dafed3b367a619bae362bf9b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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