Which versions of BlockсhainАPI are malicious?

The following NuGet versions of BlockсhainАPI are flagged malicious: 4.0.0. Treat any of these as compromised.

How do I remediate BlockсhainАPI if I installed it?

Remove BlockсhainАPI 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 BlockсhainАPI — how do I know if it already compromised me?

If BlockсhainАPI 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 BlockсhainАPI part of a known attack campaign?

Yes — BlockсhainАPI is associated with the RLMA-2024-03178, RLMA-2026-00014 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 BlockсhainАPI across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for BlockсhainАPI (version 4.0.0).

Malicious package

BlockсhainАPINuGet

Advisory published Jun 25, 2024Updated Mar 19, 2026

BlockсhainАPI is a confirmed malicious NuGet package (MAL-2024-4335) that executes malicious code on install (malicious version 4.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in BlockсhainАPI (NuGet)

MAL-2024-4335

Immediate action

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

remove BlockсhainАPI

Malicious versions

1 flagged

4.0.0

Indicators of compromise (SHA-256)

ee6f1af52b948a3b3578b73d3cb0a354880e3dd63e25562f177ed91f4d98670f

e6a04b701911066ff2232eb1397732b16c5befffe7b5dd901ffb2475bd6b5e6a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03178RLMA-2026-00014

Credits

ReversingLabs · finder

Detect & block this

O3 blocks BlockсhainАPI-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