Which versions of southwarkssrfhack are malicious?

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

How do I remediate southwarkssrfhack if I installed it?

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

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

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

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

Malicious package

southwarkssrfhackRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8851

Immediate action

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

gem uninstall southwarkssrfhack

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3938890254e979e0a5a9a1c4cf93ddc4ae7f626891694adabc1ae7b1da31bfa5

e8bb6e880973e02654a9b575b7c103969d2dfcaae76df4357e2fa5499166c4e1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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