Top issues
Detected presence of severe vulnerabilities with active exploitation.
Causes risk: actively exploited vulnerabilities
vulnerabilities
Problem
Software composition analysis has identified a component with one or more known severe vulnerabilities. Available threat intelligence telemetry has confirmed that the reported high or critical severity vulnerabilities are actively being exploited by malicious actors.Prevalence in NuGet community
0 packages
found in 
Top 100
 4 packages
found in 
Top 1k
 86 packages
found in 
Top 10k
 62067 packages
in community
Next steps
We strongly advise updating the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
Detected presence of critical severity vulnerabilities.
Causes risk: critical severity vulnerabilities
vulnerabilities
Problem
Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as critical severity.Prevalence in NuGet community
0 packages
found in 
Top 100
 3 packages
found in 
Top 1k
 47 packages
found in 
Top 10k
 21524 packages
in community
Next steps
Perform impact analysis for the reported CVEs.
We strongly advise updating the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
Detected Windows executable files compiled without following the SDL best practices while using banned string functions.
Causes risk: misconfigured toolchains detected
hardening
Problem
Security Development Lifecycle (SDL) is a group of enhanced compile-time checks that report common coding mistakes as errors. These checks prevent the use of hard-to-secure string manipulation functions. They enforce static memory access checks, and allow only the use of range-verified string parsing functions. While these checks do not prevent every memory corruption issue by themselves, they do help reduce the likelihood.Prevalence in NuGet community
0 packages
found in 
Top 100
 1 packages
found in 
Top 1k
 23 packages
found in 
Top 10k
 4708 packages
in community
Next steps
It's highly recommended to enable these checks for all software components used at security boundaries, or those that process user controlled inputs.
To enable these checks, refer to your programming language toolchain documentation.
In Microsoft VisualStudio, you can enable this feature by setting the compiler option /SDL to ON.
Detected presence of high severity vulnerabilities.
Causes risk: high severity vulnerabilities
vulnerabilities
Problem
Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as high severity.Prevalence in NuGet community
0 packages
found in 
Top 100
 4 packages
found in 
Top 1k
 115 packages
found in 
Top 10k
 88612 packages
in community
Next steps
Perform impact analysis for the reported CVEs.
Update the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
Detected Windows executable files that were compiled without following the recommended SDL process.
Causes risk: misconfigured toolchains detected
hardening
Problem
Security Development Lifecycle (SDL) is a group of enhanced compile-time checks that report common coding mistakes as errors, preventing them from reaching production. These checks minimize the number of security issues by enforcing strict memory access checks. They also prevent the use of hard-to-secure string and memory manipulation functions. To prove the binary has been compiled with these checks enabled, the compiler emits a special debug object. Removing the debug table eliminates this proof. Therefore, this check only applies to binaries that still have their debug tables.Prevalence in NuGet community
0 packages
found in 
Top 100
 3 packages
found in 
Top 1k
 47 packages
found in 
Top 10k
 13120 packages
in community
Next steps
You should keep the debug table to prove that the SDL process has been followed.
To enable these checks, refer to your programming language toolchain documentation.
In Microsoft VisualStudio, you can enable this feature by setting the compiler option /SDL to ON.
Top behaviors
Retrieves the name of the user associated with the process.
search
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in 
Top 100
 4 packages
found in 
Top 1k
 70 packages
found in 
Top 10k
 23059 packages
in community
Deletes the value of a registry key.
registry
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in 
Top 100
 1 packages
found in 
Top 1k
 26 packages
found in 
Top 10k
 6500 packages
in community
Deletes a registry key and its values.
registry
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in 
Top 100
 1 packages
found in 
Top 1k
 24 packages
found in 
Top 10k
 6811 packages
in community
Requests permission to open other processes.
permissions
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in 
Top 100
 1 packages
found in 
Top 1k
 15 packages
found in 
Top 10k
 2302 packages
in community
Requests permission required to perform a number of security-related functions, such as controlling and viewing audit messages.
permissions
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in 
Top 100
 0 packages
found in 
Top 1k
 21 packages
found in 
Top 10k
 1432 packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(2 Active Vulnerabilities)
None
2 (2 Fixable)
CVE-2022-37434c
CVE-2018-25032h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated