Which versions of swd8405 are malicious?

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

How do I remediate swd8405 if I installed it?

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

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

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

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

Malicious package

swd8405RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8934

Immediate action

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

gem uninstall swd8405

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3b328f5653b41f9849c8d40c0fd3422e4f3c8f97283f53702dac38ada5d4d0af

6c6adf0ac75217a1c8038eaae4f8a7f971ba4d4143d33cdcdae22d083ef35101

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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