Which versions of swlicap7a are malicious?

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

How do I remediate swlicap7a if I installed it?

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

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

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

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

Malicious package

swlicap7aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8939

Immediate action

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

gem uninstall swlicap7a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

527dcd59100349a7635cdf3807db047417096f13ace1abed19be49a6f45c40e6

d25c76378c617fc7deecafa14b552dfd8c7e0e6eb9d9edd3427ffd25f7745b2e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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