Which versions of swc423 are malicious?

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

How do I remediate swc423 if I installed it?

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

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

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

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

Malicious package

swc423RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8918

Immediate action

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

gem uninstall swc423

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

5cbfd3040afa89040c49f39789def1785cf45502083a39796fcc34ce5741130d

67426b6cfadf2658107ab319ddbd0fa80cda1b85f57c7f53455b86b4ee257771

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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