Which versions of resolvrtest are malicious?

The following RubyGems versions of resolvrtest are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate resolvrtest if I installed it?

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

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

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

Search your lockfiles and build artifacts for resolvrtest (version 0.0.3).

Malicious package

resolvrtestRubyGems

Advisory published Mar 18, 2026Updated Sep 24, 2026

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

Malicious code in resolvrtest (RubyGems)

MAL-2026-1921

Immediate action

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

gem uninstall resolvrtest

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

50ddeeec9e376d2b1ed76ba8bb173cc346882dc14b354cfc8cf40226fbf75cea

0d4f077106e7802f866023c9e8cfe33179f9342ace718980fc77276a6d809d0d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-00957RLUA-2026-09032

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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