Which versions of slndtskerm are malicious?

The following RubyGems versions of slndtskerm are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate slndtskerm if I installed it?

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

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

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

Search your lockfiles and build artifacts for slndtskerm (version 0.0.1).

Malicious package

slndtskermRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

slndtskerm is a confirmed malicious RubyGems package (MAL-2026-8672) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in slndtskerm (RubyGems)

MAL-2026-8672

Immediate action

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

gem uninstall slndtskerm

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

17a42b87e53b8c4c80109a6181a039da72b209247c7c3c497d75a5d659c9484b

f697c22904a399605d8d57b6634bb9ef02fc825944715308090c150b5a995330

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slndtskerm (version 0.0.1).
If you installed it — respond
Remove slndtskerm 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 slndtskerm 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. slndtskerm on RubyGems has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03323RLUA-2026-09221

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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