Which versions of proxymeta646419 are malicious?

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

How do I remediate proxymeta646419 if I installed it?

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

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

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

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

Malicious package

proxymeta646419RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8433

Immediate action

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

gem uninstall proxymeta646419

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2029ab21a455d3432af4ca87db2486d9d8791321700ef4f8da1f2d267ceabd96

f704a238250350f2d373b2d14d5bda2091192a6ceadd3ebbfc52858d5b4d500d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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