Which versions of swc422 are malicious?

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

How do I remediate swc422 if I installed it?

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

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

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

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

Malicious package

swc422RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8917

Immediate action

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

gem uninstall swc422

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ab6360c3711d263e25a4fd8c39a3f5e8e1c99f518a809636776808c2de81da00

17f0c4d95fe8649a61b78fe5d788d73651c53556b312ab156fbb43987183bc20

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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