Which versions of southwarkssrfhack4 are malicious?

The following RubyGems versions of southwarkssrfhack4 are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate southwarkssrfhack4 if I installed it?

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

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

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

Search your lockfiles and build artifacts for southwarkssrfhack4 (version 0.0.4).

Malicious package

southwarkssrfhack4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

southwarkssrfhack4 is a confirmed malicious RubyGems package (MAL-2026-8854) that executes malicious code on install (malicious version 0.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in southwarkssrfhack4 (RubyGems)

MAL-2026-8854

Immediate action

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

gem uninstall southwarkssrfhack4

Malicious versions

1 flagged

0.0.4

Indicators of compromise (SHA-256)

cccc142d5fd5bed5d981c21120ae8cc16e004615ef16ef2f36322997283973d3

1b22c0c494a5d62116e04ee92497e178a4c792de4260eb06d88c8573bcfd6499

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for southwarkssrfhack4 (version 0.0.4).
If you installed it — respond
Remove southwarkssrfhack4 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 southwarkssrfhack4 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. southwarkssrfhack4 on RubyGems has been identified as a malicious package (version 0.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03505RLUA-2026-09403

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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