Which versions of slnstep8400 are malicious?

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

How do I remediate slnstep8400 if I installed it?

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

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

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

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

Malicious package

slnstep8400RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8758

Immediate action

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

gem uninstall slnstep8400

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9f902a120368bcb2e02f48beba8e37a6718bb25dd1ae0ecf9f84c7585341a4dd

d2fc646011e23d55415702bee9c81a34c5035cf28a63641798330a0dfa7f2e20

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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