Which versions of swgitssabc are malicious?

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

How do I remediate swgitssabc if I installed it?

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

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

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

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

Malicious package

swgitssabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8936

Immediate action

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

gem uninstall swgitssabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

024959e2c87612a8f65faa014f9314c8e7e4dc5756e3a6ce53ebdca09c02950f

79bc594f6c8a80f985394fa190f6a8c1049d0245e80f584afbe3cded54186f4f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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