Which versions of verificator are malicious?

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

How do I remediate verificator if I installed it?

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

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

Yes — verificator is associated with the RLMA-2025-06636, RLUA-2026-09701 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 verificator across my projects, lockfiles, and CI pipelines?

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

Malicious package

verificatorRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

verificator is a confirmed malicious RubyGems package (MAL-2025-192925) 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 verificator (RubyGems)

MAL-2025-192925

Immediate action

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

gem uninstall verificator

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

b85af07a71d65d771844ab8e332842185979132a77e120be854480deca07e0ea

5e2c743fd2bf62dc1bd5fa8921137b053aa1559cbfe64d9c89e20f3a52e2eb34

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for verificator (version 0.0.2).
If you installed it — respond
Remove verificator 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 verificator 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. verificator 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-2025-06636RLUA-2026-09701

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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