Which versions of slnstep8250 are malicious?

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

How do I remediate slnstep8250 if I installed it?

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

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

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

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

Malicious package

slnstep8250RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8752

Immediate action

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

gem uninstall slnstep8250

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

42a50238aefe346804d868ca9b1e88078cfc605d5a467786bf99f7ca19e097e1

52093fa7e49d268d32b5e3dd048936126d989265eb3198ae581fa1b9fdafa5a4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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