Which versions of slwsvn7762 are malicious?

The following RubyGems versions of slwsvn7762 are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate slwsvn7762 if I installed it?

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

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

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

Search your lockfiles and build artifacts for slwsvn7762 (version 0.0.2).

Malicious package

slwsvn7762RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

slwsvn7762 is a confirmed malicious RubyGems package (MAL-2026-8798) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in slwsvn7762 (RubyGems)

MAL-2026-8798

Immediate action

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

gem uninstall slwsvn7762

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

a0223398a55f8f02efb0ae72bcd43b1339af9227bcf37588247135443278f1a4

f589141f4bd7b3f0d8a8a3f43c3925f338715f0f9bcb6d79937a8042920b54b7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slwsvn7762 (version 0.0.2).
If you installed it — respond
Remove slwsvn7762 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 slwsvn7762 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. slwsvn7762 on RubyGems has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03449RLUA-2026-09347

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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