Which versions of slt44107 are malicious?

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

How do I remediate slt44107 if I installed it?

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

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

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

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

Malicious package

slt44107RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8782

Immediate action

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

gem uninstall slt44107

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

1ce720425c49e19bb867b951c0545fd063c7fff1d80b31a227d7acf235ae3128

d5c78bf12541587894ddf38e273c0b3e99c7a998974b28c413a8953cbfb87813

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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