Which versions of aliseeks-api are malicious?

The following RubyGems versions of aliseeks-api are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate aliseeks-api if I installed it?

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

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

Yes — aliseeks-api is associated with the RLMA-2024-05377, RLUA-2024-09896 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 aliseeks-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aliseeks-api (version 1.0.4).

Malicious package

aliseeks-apiRubyGems

aliseeks-api is a confirmed malicious RubyGems package (MAL-2024-6571) that executes malicious code on install (malicious version 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aliseeks-api (RubyGems)

MAL-2024-6571

Immediate action

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

gem uninstall aliseeks-api

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

457a3e9b118be0e96106f48398f4e43c970e8e645025cc016805187511a82a9d

f8b8c3e3afbf84a8b2145dd9d78796ec7d934682d832a7fdb3fb53c1bbb2acc8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for aliseeks-api (version 1.0.4).
If you installed it — respond
Remove aliseeks-api 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 aliseeks-api 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. aliseeks-api on RubyGems has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05377RLUA-2024-09896

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks aliseeks-api-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