Which versions of swsubrep7a are malicious?

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

How do I remediate swsubrep7a if I installed it?

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

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

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

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

Malicious package

swsubrep7aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8961

Immediate action

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

gem uninstall swsubrep7a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d2a97f3e85b20512ad298f4c0ff59715c04f338733452d63aefc81dab7c48c52

a64a3ace87e707cc2dcc8e8e0238a40fc6f2772a0383f61a3c1eac14e6069656

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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