Which versions of mritestproxy123 are malicious?

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

How do I remediate mritestproxy123 if I installed it?

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

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

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

Search your lockfiles and build artifacts for mritestproxy123 (4 malicious versions).

Malicious package

mritestproxy123RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8094

Immediate action

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

gem uninstall mritestproxy123

Malicious versions

4 flagged

0.0.10.0.20.0.30.0.4

Indicators of compromise (SHA-256)

dd85b271ba58bd5b197dc80f94155aa0bd9f84e0e2e3051bc49b8936ce671e59

934c1c009f6ae3c179f641463eb9e16fca5a794054f7b110dbc279c8f5c77291

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02745RLUA-2026-08605

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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