Which versions of slnstep8475 are malicious?

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

How do I remediate slnstep8475 if I installed it?

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

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

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

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

Malicious package

slnstep8475RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8761

Immediate action

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

gem uninstall slnstep8475

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

98a2e4010d1cbc4ce41825094d669e2f67ea2f00dd0e90d1247c602acf67a8aa

73d147ada2cbc7ca0181a86f568929dc7cfea6ab31714fa910380181bb6166dd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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