Which versions of slnstep8350 are malicious?

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

How do I remediate slnstep8350 if I installed it?

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

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

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

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

Malicious package

slnstep8350RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8756

Immediate action

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

gem uninstall slnstep8350

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2fa20c23f11fcc908cadb255848e70f4f20245d4deede1fc47364a9953531989

a98fa1403a9fd72055bceca725b30f5d8d9e7c9af875114dc0a548acbde27b71

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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