Which versions of gtest1778553427 are malicious?

The following RubyGems versions of gtest1778553427 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate gtest1778553427 if I installed it?

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

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

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

Search your lockfiles and build artifacts for gtest1778553427 (version 0.0.1).

Malicious package

gtest1778553427RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in gtest1778553427 (RubyGems)

MAL-2026-7723

Immediate action

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

gem uninstall gtest1778553427

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1c078a3d210f6bb6c27729b87a48a7c85cba39f266ed761fb528ecd51978bb4c

0eeed3e1bac96e8758959100ac5dc8a7b86c225ff29d82019c51070eff0913ca

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02374RLUA-2026-08165

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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