Which versions of probervdgcosw are malicious?

The following RubyGems versions of probervdgcosw are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate probervdgcosw if I installed it?

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

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

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

Search your lockfiles and build artifacts for probervdgcosw (version 0.0.2).

Malicious package

probervdgcoswRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

probervdgcosw is a confirmed malicious RubyGems package (MAL-2026-8428) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in probervdgcosw (RubyGems)

MAL-2026-8428

Immediate action

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

gem uninstall probervdgcosw

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

bae95c4528522f070a1674b778efe520c805dab043b6020e74420d48a4d29606

02282ac8b58fc1b8ff4df6e6118d876207b11f908da992789eabf64bda9037a4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03079RLUA-2026-08952

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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