Which versions of slt71879 are malicious?

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

How do I remediate slt71879 if I installed it?

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

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

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

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

Malicious package

slt71879RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8783

Immediate action

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

gem uninstall slt71879

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

94ad5a113fa8452633dde25e4d7e55201d19484576e7ff858af65f077e41e4f1

948aa79c4aa6e251ced71e97d40177d10ef391f0f86d48d0856c12d8ca699397

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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