Which versions of tmpojrljqbwjgabc are malicious?

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

How do I remediate tmpojrljqbwjgabc if I installed it?

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

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

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

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

Malicious package

tmpojrljqbwjgabcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9000

Immediate action

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

gem uninstall tmpojrljqbwjgabc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

25832c779c147ec533c6db79f00cb3cdef7daf145acf87527c0bd5ef8a6b685e

22fc94466cdbd0c92bd958a5efe5d268d82458df7ac2faaf54c1ebe1c086229c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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