Which versions of slt81847 are malicious?

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

How do I remediate slt81847 if I installed it?

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

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

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

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

Malicious package

slt81847RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8785

Immediate action

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

gem uninstall slt81847

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

ab0039961f6a806a220f52ff2cce04ae1ceb9c2ad28d17acf4c4464cb54724fc

fb1f223119d330fcf8084d25f3041334a7819043c2413864a425d2b7df9896b1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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