Which versions of goproxylondonx are malicious?

The following RubyGems versions of goproxylondonx are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5. Treat any of these as compromised.

How do I remediate goproxylondonx if I installed it?

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

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

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

Search your lockfiles and build artifacts for goproxylondonx (5 malicious versions).

Malicious package

goproxylondonxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

goproxylondonx is a confirmed malicious RubyGems package (MAL-2026-7716) that executes malicious code on install (malicious versions 0.0.1, 0.0.2, 0.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in goproxylondonx (RubyGems)

MAL-2026-7716

Immediate action

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

gem uninstall goproxylondonx

Malicious versions

5 flagged

0.0.10.0.20.0.30.0.40.0.5

Indicators of compromise (SHA-256)

a847eb27d1089b3e182a8f5cc88023fa099fb2543a96445fdbfb58fa992e00cd

9663be78cb62b91837fb53755775a49f8fcacbc38490579fa4f2c786e0cb3603

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02367RLUA-2026-08158

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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