Which versions of slnmodtestabc are malicious?

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

How do I remediate slnmodtestabc if I installed it?

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

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

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

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

Malicious package

slnmodtestabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8696

Immediate action

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

gem uninstall slnmodtestabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a9711c1c1197c977c2233185e69030eb7fad857d9a94c6d8be899c6de30562cd

3cecc6bef42b059f52d14378414d187e3316335cb3d8aa0dfe5a4b1db44b79dc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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