Which versions of fortnite-api are malicious?

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

How do I remediate fortnite-api if I installed it?

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

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

Yes — fortnite-api is associated with the RLMA-2024-05730, RLUA-2024-10249, RLUA-2026-08115 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 fortnite-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fortnite-api (version 0.2.0).

Malicious package

fortnite-apiRubyGems

fortnite-api is a confirmed malicious RubyGems package (MAL-2024-6924) 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 fortnite-api (RubyGems)

MAL-2024-6924

Immediate action

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

gem uninstall fortnite-api

Malicious versions

1 flagged

0.2.0

Indicators of compromise (SHA-256)

dfdb235362c019f39f93c93b4a0f29e4f8a5fa4c79c9bb5bec46c4237a8e0d8d

721a7aeae96ee7eb70d05e3aafc68ea4fb00e67e18295c4702015b19984c363b

4b3afbd68b1dc8fd9327ea1d0fdbca3bd9059313f7432bab9fbfb6e7ba138048

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for fortnite-api (version 0.2.0).
If you installed it — respond
Remove fortnite-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 fortnite-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. fortnite-api 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-05730RLUA-2024-10249RLUA-2026-08115

References

Credits

ReversingLabs · finder

Detect & block this

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