Which versions of aidoklxlhvfkeq are malicious?

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

How do I remediate aidoklxlhvfkeq if I installed it?

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

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

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

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

Malicious package

aidoklxlhvfkeqRubyGems

Advisory published Jul 7, 2026Updated Jul 23, 2026

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

MAL-2026-7484

Immediate action

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

gem uninstall aidoklxlhvfkeq

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fa8f39f0268908625133080b1e1ca542c00ebf2641d885b7432bfd7c0cf75c78

Detection & response playbook

Malicious package

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

Credits

ReversingLabs · finder

Detect & block this

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