Which versions of proxymeta646478 are malicious?

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

How do I remediate proxymeta646478 if I installed it?

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

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

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

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

Malicious package

proxymeta646478RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8436

Immediate action

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

gem uninstall proxymeta646478

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a524ea4be7c7fe84dd70e12e8f104cb01363234ef7587600720d47bf9a6dc167

8c1daff5718d316211e878a3126b6391a5c16722912f58241f2203300c43fdbf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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