Which versions of swaim6a are malicious?

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

How do I remediate swaim6a if I installed it?

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

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

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

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

Malicious package

swaim6aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8914

Immediate action

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

gem uninstall swaim6a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

26f032caf3bd578ac1ce1479b31ba486a6a1447c6019e68400bf4c4b05e67e36

c41ed11c0219b31ec5bb1ebe87bc0c5fea378e056cfb4b80665d451c8b1412bd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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