Which versions of swd8249t are malicious?

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

How do I remediate swd8249t if I installed it?

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

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

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

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

Malicious package

swd8249tRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8932

Immediate action

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

gem uninstall swd8249t

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ae84cd81d17db3ba761b76349cc1cf0ef1dfde87a3c922000e9b0f94018cde3d

0f38e0e826088815baa2f38ff748a74ab946aed0f40861d5620f67df5955b270

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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