Which versions of slt27395 are malicious?

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

How do I remediate slt27395 if I installed it?

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

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

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

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

Malicious package

slt27395RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8779

Immediate action

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

gem uninstall slt27395

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

f84b044bf304f6284de56c4e5573b7ef0b78069485e42760fddb15b5480ce2e4

4a02866bff8bff54c62999026cc29551a93c15d3b9abd751e704937a7928027e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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