Which versions of mytemptest1778551000 are malicious?

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

How do I remediate mytemptest1778551000 if I installed it?

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

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

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

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

Malicious package

mytemptest1778551000RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8114

Immediate action

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

gem uninstall mytemptest1778551000

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

75e8632e4e4142fd0d7b4fda30d91fa45ae71b1442140c49cd5d4262ac2bd898

28caf7cc1b004becb724146c1b9f754d87b4eaf1263946872a75ee5c3dbb0091

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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