Which versions of slwgit2027 are malicious?

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

How do I remediate slwgit2027 if I installed it?

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

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

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

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

Malicious package

slwgit2027RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8795

Immediate action

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

gem uninstall slwgit2027

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

350313c06107e3b33350443d266e63485a2b69388f5a87e8c87045c9df4a9383

c78c0c72e83919a0ea472f19bdd84ff265121c57ba7be97e1a9858f8a575aba5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slwgit2027 (version 0.0.2).
If you installed it — respond
Remove slwgit2027 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 slwgit2027 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. slwgit2027 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-03446RLUA-2026-09344

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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