Which versions of swc424 are malicious?

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

How do I remediate swc424 if I installed it?

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

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

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

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

Malicious package

swc424RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8919

Immediate action

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

gem uninstall swc424

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

4864364b04981a2d1262fd7e87070459d3e4c2f3049d39b3822ea6d1e2927955

389f2070b232d0bfd18aee168a4c478b77afd1e6011e335dcab079f080abbef9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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