Which versions of proxymeta646420 are malicious?

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

How do I remediate proxymeta646420 if I installed it?

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

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

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

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

Malicious package

proxymeta646420RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8434

Immediate action

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

gem uninstall proxymeta646420

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5f73578fa383c814bb20a38b6d96c80076f40fb1d9d9f2276d30ed876d189ba7

5a70242d3c95506e3d69b493594be8f2f8753b99c616bf55466e7fd1f2d0ced8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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