Which versions of slnstep8325 are malicious?

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

How do I remediate slnstep8325 if I installed it?

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

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

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

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

Malicious package

slnstep8325RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8755

Immediate action

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

gem uninstall slnstep8325

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

120aff110067c0719c966005dd7b5a85e2b2f12ecf3d66cdc09c95ec7f242bbc

7185cd8ea5922d8b78ef028a6203341eeffc74f16f2f0fb51493f59e48c98872

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slnstep8325 (version 0.0.1).
If you installed it — respond
Remove slnstep8325 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 slnstep8325 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. slnstep8325 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-03406RLUA-2026-09304

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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