Which versions of wpfuihelpercore are malicious?

The following NuGet versions of wpfuihelpercore are flagged malicious: 1.0.0, 1.0.2. Treat any of these as compromised.

How do I remediate wpfuihelpercore if I installed it?

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

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

Yes — wpfuihelpercore is associated with the RLMA-2026-02065 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 wpfuihelpercore across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for wpfuihelpercore (2 malicious versions).

Malicious package

wpfuihelpercoreNuGet

Advisory published Apr 16, 2026Updated Apr 16, 2026

wpfuihelpercore is a confirmed malicious NuGet package (MAL-2026-2808) that executes malicious code on install (malicious versions 1.0.0, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wpfuihelpercore (NuGet)

MAL-2026-2808

Immediate action

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

remove wpfuihelpercore

Malicious versions

2 flagged

1.0.01.0.2

Indicators of compromise (SHA-256)

da4568e9b856e5df72ba69ec577935aa2423d663641c498570cff0e27d51653a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02065

Credits

ReversingLabs · finder

Detect & block this

O3 blocks wpfuihelpercore-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