Which versions of alidayu-api are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for alidayu-api (version 0.0.2).

Malicious package

alidayu-apiRubyGems

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

Malicious code in alidayu-api (RubyGems)

MAL-2024-6565

Immediate action

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

gem uninstall alidayu-api

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

20933f42ba6d02c2cdf37a3b3fcbf838ab62dab42ec66e385edefb9719501dc6

f60c115076787780e53410278d2453a52b2f762ea366bae9ac53727682673086

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05371RLUA-2024-09890

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

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