Which versions of slnx759593 are malicious?

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

How do I remediate slnx759593 if I installed it?

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

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

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

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

Malicious package

slnx759593RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8767

Immediate action

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

gem uninstall slnx759593

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

28fbda6fed8557c4de7ac560249e5226b885da8c1611af08bc73ccb7eb734a14

79962fcf334fc96570a19227fdc2c23a6670aa2661df48309d441787b40fb4ef

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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