Which versions of swmtry are malicious?

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

How do I remediate swmtry if I installed it?

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

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

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

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

Malicious package

swmtryRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8949

Immediate action

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

gem uninstall swmtry

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8d011dfddb9e5ab12460daed27cd6470a97c12b98f437c380b791da39fd8120e

cd1492d826019ba755ebee9c6a7f54727410823133936debeba7723aeff5e253

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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