Which versions of slnstep8275 are malicious?

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

How do I remediate slnstep8275 if I installed it?

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

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

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

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

Malicious package

slnstep8275RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8753

Immediate action

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

gem uninstall slnstep8275

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d7e21174d17d32e3d3c25d4d773dc9701653acdf5e8fa7afb4aff9743d356c32

7bf00aff8f3ad6d0730c3de402df419ef375d4d272453f9c76aff376eca7a452

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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