Which versions of cordova_rake are malicious?

The following RubyGems versions of cordova_rake are flagged malicious: 0.5.2. Treat any of these as compromised.

How do I remediate cordova_rake if I installed it?

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

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

Yes — cordova_rake is associated with the RLMA-2024-05649, RLUA-2024-10168, RLUA-2026-07944 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 cordova_rake across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cordova_rake (version 0.5.2).

Malicious package

cordova_rakeRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in cordova_rake (RubyGems)

MAL-2024-6843

Immediate action

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

gem uninstall cordova_rake

Malicious versions

1 flagged

0.5.2

Indicators of compromise (SHA-256)

63acda108d61054e32cee237aceeec89663dc69db5eb5431093605092ffd9122

ea3efd9f5fd2226cbbac709f8b1484c13ec78e4010f9a3d92b25b8ff7e460ab0

02b074d1502815460b3a603ccb6ed12ecd6a4e80eb7b332216d08229fb8fa0a3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05649RLUA-2024-10168RLUA-2026-07944

References

Credits

ReversingLabs · finder

Detect & block this

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