Which versions of fooaid503724d are malicious?

The following RubyGems versions of fooaid503724d are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate fooaid503724d if I installed it?

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

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

Yes — fooaid503724d is associated with the RLMA-2026-02338, RLUA-2026-08111 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 fooaid503724d across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fooaid503724d (version 0.0.1).

Malicious package

fooaid503724dRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

fooaid503724d is a confirmed malicious RubyGems package (MAL-2026-7687) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fooaid503724d (RubyGems)

MAL-2026-7687

Immediate action

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

gem uninstall fooaid503724d

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

81c10727bf51ea4c9e3af58ac40f44811f5f45f4280fdc3487d9c1137f16e1d5

2f1efbe5a6278efaa6b559151cc6e0582e93f67f4ad1fdc16ec7d1c4f3957f70

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02338RLUA-2026-08111

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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