Which versions of slnstep8300 are malicious?

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

How do I remediate slnstep8300 if I installed it?

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

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

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

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

Malicious package

slnstep8300RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8754

Immediate action

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

gem uninstall slnstep8300

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d7331c500a496ee931deeec45c47a1e1de6f5aef34b49c6f12d2d604fd5dda5b

4d22231890c43587e1da627ef5d7a7ae1ba837aeff88092b8b60cf283d7d77ca

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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