Which versions of probejiqptzco are malicious?

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

How do I remediate probejiqptzco if I installed it?

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

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

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

Search your lockfiles and build artifacts for probejiqptzco (6 malicious versions).

Malicious package

probejiqptzcoRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8427

Immediate action

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

gem uninstall probejiqptzco

Malicious versions

6 flagged

0.0.10.0.20.0.30.0.40.0.50.0.6

Indicators of compromise (SHA-256)

c7f62661511cbea482b8c60a9510112dc6b7e92b3d3f801f73cbcefce6731b80

db674bc1f54b4f1cab74a4780abd6e0ef417f71780b746b85f7c197fbda40577

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for probejiqptzco (6 malicious versions).
If you installed it — respond
Remove probejiqptzco 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 probejiqptzco 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. probejiqptzco 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, 0.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03078RLUA-2026-08951

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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