Which versions of slt43158 are malicious?

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

How do I remediate slt43158 if I installed it?

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

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

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

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

Malicious package

slt43158RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8781

Immediate action

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

gem uninstall slt43158

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

0536b233b42e4e021d3e2233ac1e6722b984287510464cb0932815013a720ce3

9215e30a0e87f17570ed48825f9176ea9a4b2a98cbfffdf153629b6aa27a1c66

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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