Which versions of danger_apkstats are malicious?

The following RubyGems versions of danger_apkstats are flagged malicious: 0.2.0. Treat any of these as compromised.

How do I remediate danger_apkstats if I installed it?

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

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

Yes — danger_apkstats is associated with the RLMA-2024-05659, RLUA-2024-10178, RLUA-2026-07957 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_apkstats across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for danger_apkstats (version 0.2.0).

Malicious package

danger_apkstatsRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in danger_apkstats (RubyGems)

MAL-2024-6853

Immediate action

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

gem uninstall danger_apkstats

Malicious versions

1 flagged

0.2.0

Indicators of compromise (SHA-256)

ac429b201dae722b30fbaf0ff3c602621369e6cb3c2558354436f9159d0ab46b

a7d9bdcd08e8d3c20680aea591a7cc72a0b0b9f1066ba4d50a4ceef61784c934

d3a399aed88cb2133b98e81c7cddb1caff71b7ac4fa8a0e1f7bad0abacbcdbe7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05659RLUA-2024-10178RLUA-2026-07957

References

Credits

ReversingLabs · finder

Detect & block this

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