Which versions of swwsdl2 are malicious?

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

How do I remediate swwsdl2 if I installed it?

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

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

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

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

Malicious package

swwsdl2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8963

Immediate action

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

gem uninstall swwsdl2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7999877472269a41ce0082ac818150b0521623a17edc671caecc05cf4fbaf76a

2ae7f2c83af6da86ead955d48c8ec7db6f28bfb53b23eb4e5599e7b844625ce3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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