Which versions of royal-mail_api are malicious?

The following RubyGems versions of royal-mail_api are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate royal-mail_api if I installed it?

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

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

Yes — royal-mail_api is associated with the RLMA-2024-05819, RLUA-2024-10340, RLUA-2026-09083 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 royal-mail_api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for royal-mail_api (version 0.1.1).

Malicious package

royal-mail_apiRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in royal-mail_api (RubyGems)

MAL-2024-7014

Immediate action

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

gem uninstall royal-mail_api

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

3445eeb1c754ce413f2ca22c2f021b44b32e4f31bf7571e06ba23c2a185bc748

6c588c136019ffac2c77235c0c98ddf1247023fa01ce1416c71a4cfa7140f7ae

b6cd0c2b89472106b19ffb5ca43a8fb5fbb969ca8360b0daaf34b8267b583ba7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05819RLUA-2024-10340RLUA-2026-09083

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks royal-mail_api-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