Which versions of fossa-curl-test are malicious?

The following RubyGems versions of fossa-curl-test are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate fossa-curl-test if I installed it?

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

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

Yes — fossa-curl-test is associated with the RLMA-2024-05731, RLUA-2024-10250, RLUA-2026-08116 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 fossa-curl-test across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fossa-curl-test (version 0.0.3).

Malicious package

fossa-curl-testRubyGems

fossa-curl-test is a confirmed malicious RubyGems package (MAL-2024-6925) that executes malicious code on install (malicious version 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fossa-curl-test (RubyGems)

MAL-2024-6925

Immediate action

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

gem uninstall fossa-curl-test

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

7021796f976d200527ad9d5f03a6eacc5e06fab4214211e19aa4aa663551764c

4efc806b36320884b63a575101af3bdaff0755c20de8e16aeb9b95f57933e8b0

cdfad87c6ea0a2cf8fd39360c91001d017a1d789b3b318053efb0e35309d0167

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05731RLUA-2024-10250RLUA-2026-08116

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks fossa-curl-test-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