HighNuGet0 affected versions

Portable.Xaml.Net

Portable.Xaml.Net has 0 versions on NuGet.org flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with dotnet list package.

The incident that flagged it

High20 Jul 2026

GitHub Advisory backfill sweep - ~264 NuGet CWE-506 malware advisories dominated by Solana wallet impersonators, WPF/WinForms UI-kit typosquats, and popular-API impersonators (Zendesk, Binance, Coinbase, Ripple, Stripe, PayPal, Kraken, Kucoin, Huobi, Bybit)

On 2026-07-20 GitHub's Advisory Database published a ~264-package NuGet CWE-506 malware backfill - the largest single-day NuGet sweep on record. Dominant themes: Solana/crypto wallet impersonators (~15 packages: Solana, SolanaWallet, solananet, solnetplus, solnetall, solnetunified, solnetwallet.net.core), WPF/WinForms UI-kit typosquats (~40 packages: WPF-UI-Net, WpfAnimatedGif.Net, WpfLightToolkit.Net, LiveCharts.net, Bunifu.*), Oracle Cloud SDK impersonators (OCI.DotNetSDK.*, ~25 packages), and crypto-exchange API impersonators (Binance, Kucoin, Kraken, Bybit, Coinbase, Huobi, Ripple).

Versions named here:

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

Portable.Xaml.Net is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. We don't parse NuGet manifests yet, but the incident write-ups list every affected package.

Browse the incident feed All flagged NuGet packages

Other packages in the same incident

If Portable.Xaml.Net is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.