Which versions of Kraken.Exchange are malicious?

The following NuGet versions of Kraken.Exchange are flagged malicious: 4.1.1, 4.1.2, 4.1.3. Treat any of these as compromised.

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

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

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

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

Search your lockfiles and build artifacts for Kraken.Exchange (3 malicious versions).

Malicious package

Kraken.ExchangeNuGet

Kraken.Exchange is a confirmed malicious NuGet package (MAL-2024-4522) that executes malicious code on install (malicious versions 4.1.1, 4.1.2, 4.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in Kraken.Exchange (NuGet)

MAL-2024-4522

Immediate action

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

remove Kraken.Exchange

Malicious versions

3 flagged

4.1.14.1.24.1.3

Indicators of compromise (SHA-256)

266ae6df163c511d8d1af1287041b5e098d0befd8284829236187a60bb4f2da8

9f50d3a588a07af963badbdd41596f5b8930dda0bedbcc6655981a31506882bc

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for Kraken.Exchange (3 malicious versions).
If you installed it — respond
Remove Kraken.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 Kraken.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. Kraken.Exchange on NuGet has been identified as a malicious package (versions 4.1.1, 4.1.2, 4.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03307RLUA-2024-07672

References

reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks Kraken.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