Which versions of cocoapod are malicious?

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

How do I remediate cocoapod if I installed it?

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

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

Yes — cocoapod is associated with the RLMA-2025-06611, RLUA-2026-07934 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 cocoapod across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cocoapod (version 0.0.2).

Malicious package

cocoapodRubyGems

Advisory published Dec 23, 2025Updated Sep 24, 2026

cocoapod is a confirmed malicious RubyGems package (MAL-2025-192904) 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 cocoapod (RubyGems)

MAL-2025-192904

Immediate action

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

gem uninstall cocoapod

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

6e39c1f1d818680bf4597cac53387b3fb411ea34c024fb9975c407b83ef07a6d

02e4cb6990d6c930bac40c32ac584dab1bf7860a12bae8a02c87d84d2a611e0d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cocoapod (version 0.0.2).
If you installed it — respond
Remove cocoapod 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 cocoapod 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. cocoapod 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-2025-06611RLUA-2026-07934

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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