Which versions of danger-ios-logs are malicious?

The following RubyGems versions of danger-ios-logs are flagged malicious: 0.1.2. Treat any of these as compromised.

How do I remediate danger-ios-logs if I installed it?

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

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

Yes — danger-ios-logs is associated with the RLMA-2024-05658, RLUA-2024-10177, RLUA-2026-07956 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 danger-ios-logs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for danger-ios-logs (version 0.1.2).

Malicious package

danger-ios-logsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

danger-ios-logs is a confirmed malicious RubyGems package (MAL-2024-6852) that executes malicious code on install (malicious version 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in danger-ios-logs (RubyGems)

MAL-2024-6852

Immediate action

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

gem uninstall danger-ios-logs

Malicious versions

1 flagged

0.1.2

Indicators of compromise (SHA-256)

e290bbdaf156cd3912b5c5d91089d90e8184435462a3043d07b8e3ff74b5b9d8

47b84f3236aea92836f7fd6619338276b0694c407b956603fc37fc3ab0057f0e

32ebe7c680a1c5757bef7fadfffc038a332460aadaecd53990a5762161ca3d44

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05658RLUA-2024-10177RLUA-2026-07956

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks danger-ios-logs-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