Which versions of gtest1778553438 are malicious?

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

How do I remediate gtest1778553438 if I installed it?

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

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

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

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

Malicious package

gtest1778553438RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7725

Immediate action

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

gem uninstall gtest1778553438

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1d4acadece24cc8847056dda3e21eae95275085fe7f364d3489896577ce63699

8f36e55496a8911e9b81ecdea5397d2b9248e013fbfa648f6dede6b1f56a7cef

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for gtest1778553438 (version 0.0.1).
If you installed it — respond
Remove gtest1778553438 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 gtest1778553438 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. gtest1778553438 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-02376RLUA-2026-08167

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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