Which versions of admiral-stats_parser are malicious?

The following RubyGems versions of admiral-stats_parser are flagged malicious: 1.17.1. Treat any of these as compromised.

How do I remediate admiral-stats_parser if I installed it?

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

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

Yes — admiral-stats_parser is associated with the RLMA-2024-05324, RLUA-2024-09843 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 admiral-stats_parser across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for admiral-stats_parser (version 1.17.1).

Malicious package

admiral-stats_parserRubyGems

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

Malicious code in admiral-stats_parser (RubyGems)

MAL-2024-6518

Immediate action

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

gem uninstall admiral-stats_parser

Malicious versions

1 flagged

1.17.1

Indicators of compromise (SHA-256)

6df0f3266aae7e8a709c0ad82dd762734a5a42826421c51f5aff21e38c1e3426

c089fdc7fc1546323b0bd34b5dccdb65292af8366f87e8b22eab8646b9529c83

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05324RLUA-2024-09843

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks admiral-stats_parser-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