Which versions of swm8405 are malicious?

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

How do I remediate swm8405 if I installed it?

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

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

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

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

Malicious package

swm8405RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8945

Immediate action

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

gem uninstall swm8405

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3d89e83e71617488afcbe59f1577b27c566e9352141ce289cc99f3b185d14c4b

45a9144d9b375d4226ebd53526cb7a0e7ba3fdfd1f1369ef2125ee61e062c1dc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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