Which versions of zztxtwtmp14 are malicious?

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

How do I remediate zztxtwtmp14 if I installed it?

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

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

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

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

Malicious package

zztxtwtmp14RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-10001

Immediate action

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

gem uninstall zztxtwtmp14

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

aea1168aceb11a51db8314253721781d8ce3357937392e60c732b494f8d82f8c

4c968818cbb403bf5249e4e03ea93d262fedc5ede0f96589606dcccbe1d68e28

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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