Which versions of rxsouthmeet are malicious?

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

How do I remediate rxsouthmeet if I installed it?

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

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

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

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

Malicious package

rxsouthmeetRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8552

Immediate action

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

gem uninstall rxsouthmeet

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

88fa84bb649f4c34701dd4b1390227ceba58929dd26f1e27600f70df759861d5

3ce9f761790a5a9807cf6612870779329b72a9b077bd17df872a8ec17dca8dc6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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