Which versions of swi6133 are malicious?

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

How do I remediate swi6133 if I installed it?

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

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

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

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

Malicious package

swi6133RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8937

Immediate action

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

gem uninstall swi6133

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5073073ec9dc1f7e2c9eb299795938094080a2f3deeffe9274d606e87e5212db

d5415346ff4af326db7b2386b054b4c3f262ce94c2c17feb7967b8b9a51ed6de

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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