Which versions of ptrsec_rce_test are malicious?

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

How do I remediate ptrsec_rce_test if I installed it?

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

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

Yes — ptrsec_rce_test is associated with the RLMA-2024-05811, RLUA-2024-10332, RLUA-2026-08996 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 ptrsec_rce_test across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ptrsec_rce_test (5 malicious versions).

Malicious package

ptrsec_rce_testRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

ptrsec_rce_test is a confirmed malicious RubyGems package (MAL-2024-7005) 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 ptrsec_rce_test (RubyGems)

MAL-2024-7005

Immediate action

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

gem uninstall ptrsec_rce_test

Malicious versions

5 flagged

0.0.10.0.20.0.30.0.40.0.5

Indicators of compromise (SHA-256)

0401453c64fe3a73ce7b5813532c58a3950122c9fc21a02a1273075426bf131a

e8ea4a6b63b48a8d6c3738053a307f631c51b4a5e165dba19cf6180f7515e7e9

be07e2addd9d8727736fb945aa14213a8e69716121a2f1ddf7220a45501fdea9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05811RLUA-2024-10332RLUA-2026-08996

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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