Which versions of slnhack1778549948 are malicious?

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

How do I remediate slnhack1778549948 if I installed it?

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

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

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

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

Malicious package

slnhack1778549948RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8683

Immediate action

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

gem uninstall slnhack1778549948

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2e47364d800fc9f5e8eecb1a1d31d1d2d8cab8217d99c4e683968b105926ed5d

340055686334ed29427f53d3115f921d0f3e6bd16cfde0413e922beaa962299c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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