Which versions of xsouthcal1 are malicious?

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

How do I remediate xsouthcal1 if I installed it?

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

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

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

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

Malicious package

xsouthcal1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9537

Immediate action

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

gem uninstall xsouthcal1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ab4e488b21371b306c6e6ba9103825adc5c70822cc4b122102ef1dd58809ce1b

057ccdfe16a8db31336f53591e17558fd88c242db73adac2eb056f1b1ea23b16

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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