Which versions of proxymeta646423 are malicious?

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

How do I remediate proxymeta646423 if I installed it?

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

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

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

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

Malicious package

proxymeta646423RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8435

Immediate action

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

gem uninstall proxymeta646423

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b7eb79f2afa7816556d5fecd96ff364dd2b1985caee7e64850b5a92083239193

357c95aaca79facfcbb3982db7962fc7b2243c5b3ecf7042e86bb2ea3bc42b68

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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