Which versions of prx1b49033905 are malicious?

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

How do I remediate prx1b49033905 if I installed it?

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

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

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

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

Malicious package

prx1b49033905RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8456

Immediate action

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

gem uninstall prx1b49033905

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4f2bcf072486712fb6f17791735e2ea53af91d55709ccfc8e639ca9b10bb7592

b0a4b943f5674575b3a9293e6b20db577626ca6941db0871abeeefcaeb35b232

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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