Which versions of swd8249a are malicious?

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

How do I remediate swd8249a if I installed it?

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

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

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

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

Malicious package

swd8249aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8931

Immediate action

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

gem uninstall swd8249a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

41975d544d57f5287a75afd3a4c03e7150c6e7ba0a48b84940f316adfe3288e3

698ade815cae0e16b76e5453fb71ca613e71ed3406677f0d24d53c91575e47bb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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