Which versions of Blоckcore.Featսres.SignalR are malicious?

The following NuGet versions of Blоckcore.Featսres.SignalR are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate Blоckcore.Featսres.SignalR if I installed it?

Remove Blоckcore.Featսres.SignalR 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 Blоckcore.Featսres.SignalR — how do I know if it already compromised me?

If Blоckcore.Featսres.SignalR 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 Blоckcore.Featսres.SignalR part of a known attack campaign?

Yes — Blоckcore.Featսres.SignalR is associated with the RLMA-2024-03156 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 Blоckcore.Featսres.SignalR across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for Blоckcore.Featսres.SignalR (version 1.0.7).

Malicious package

Blоckcore.Featսres.SignalRNuGet

Blоckcore.Featսres.SignalR is a confirmed malicious NuGet package (MAL-2024-4360) that executes malicious code on install (malicious version 1.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in Blоckcore.Featսres.SignalR (NuGet)

MAL-2024-4360

Immediate action

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

remove Blоckcore.Featսres.SignalR

Malicious versions

1 flagged

1.0.7

Indicators of compromise (SHA-256)

bea13e3eb519d14616a46e4bfb159e7aeb22a2b90bf9c1105f075db9de009788

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03156

Credits

ReversingLabs · finder

Detect & block this

O3 blocks Blоckcore.Featսres.SignalR-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