How do I remediate Crypto.Exchange if I installed it?

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

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

Yes — Crypto.Exchange is associated with the RLMA-2024-03247, RLUA-2024-07658 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 Crypto.Exchange across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for Crypto.Exchange (61 malicious versions).

Malicious package

Crypto.ExchangeNuGet

Crypto.Exchange is a confirmed malicious NuGet package (MAL-2024-4454) that executes malicious code on install (malicious versions 1.2.1, 1.2.2, 1.2.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in Crypto.Exchange (NuGet)

MAL-2024-4454

Immediate action

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

remove Crypto.Exchange

Malicious versions

61 flagged

1.2.11.2.21.2.31.2.41.2.51.2.61.2.71.2.81.2.91.2.101.2.111.2.121.2.131.2.141.2.151.2.161.2.171.2.181.2.191.2.201.2.211.2.221.2.231.2.241.2.251.2.261.2.271.2.281.2.291.2.301.2.311.2.321.2.331.2.341.2.351.2.361.2.371.2.381.2.391.2.401.2.411.2.421.2.431.2.441.2.451.2.461.2.471.2.481.2.491.2.501.2.511.2.521.2.531.2.541.2.551.2.566.2.16.2.26.2.46.3.46.3.5

Indicators of compromise (SHA-256)

9f042da3a302a2e9d8e5a5f11b1132a859f74b3f63cc74c6e9fb7624097400e7

0d860bf186fddaa1d550145c408c3c2ee38c5f5d3421a0aa46efd6c5d176bd76

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for Crypto.Exchange (61 malicious versions).
If you installed it — respond
Remove Crypto.Exchange 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 Crypto.Exchange 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. Crypto.Exchange on NuGet has been identified as a malicious package (versions 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.2.8, and 53 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03247RLUA-2024-07658

References

reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks Crypto.Exchange-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