Which versions of swlicrep6a are malicious?

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

How do I remediate swlicrep6a if I installed it?

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

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

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

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

Malicious package

swlicrep6aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8941

Immediate action

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

gem uninstall swlicrep6a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bd4445f201dfef4b48cccf0d22edb40f3fec3aacdcd8196afb576c79d09f139e

a9615ade70423f70f95e0a36a3d42a43ffa19388e48d7f390bab84f36c5b1e2e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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