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 PowerShell Gallery community
2 packages
found in
Top 100
26 packages
found in
Top 1k
118 packages
found in
Top 10k
190 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 PowerShell Gallery community
2 packages
found in
Top 100
21 packages
found in
Top 1k
107 packages
found in
Top 10k
170 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 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 PowerShell Gallery community
2 packages
found in
Top 100
27 packages
found in
Top 1k
118 packages
found in
Top 10k
195 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 PowerShell Gallery community
3 packages
found in
Top 100
39 packages
found in
Top 1k
188 packages
found in
Top 10k
322 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.
Detected Windows executable files compiled without following the SDL best practices while using banned memory 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 memory manipulation functions. They enforce static memory access checks, and allow only the use of range-verified memory access functions. While these checks do not prevent every memory corruption issue by themselves, they do help reduce the likelihood.Prevalence in PowerShell Gallery community
1 packages
found in
Top 100
14 packages
found in
Top 1k
43 packages
found in
Top 10k
86 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.
Top behaviors
Tampers with system firmware environment variables.
settings
Prevalence in PowerShell Gallery community
Behavior commonly used by malicious software (Important)
Behavior often found in this community (Common)
2 packages
found in
Top 100
2 packages
found in
Top 1k
2 packages
found in
Top 10k
6 packages
in community
Loads additional snap-ins or modules to the current session.
payload
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
90 packages
found in
Top 100
509 packages
found in
Top 1k
3113 packages
found in
Top 10k
5185 packages
in community
Tampers with Windows PowerShell Desired State Configuration (DSC).
execution
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
3 packages
found in
Top 100
80 packages
found in
Top 1k
183 packages
found in
Top 10k
289 packages
in community
Interacts with Microsoft .NET Framework code, types and assemblies.
execution
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
100 packages
found in
Top 100
804 packages
found in
Top 1k
6518 packages
found in
Top 10k
11726 packages
in community
Enumerates system firmware tables.
search
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
1 packages
found in
Top 100
6 packages
found in
Top 1k
10 packages
found in
Top 10k
21 packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(3 Active Vulnerabilities)
None
3 (3 Fixable)
CVE-2024-56171c
CVE-2024-40896c
CVE-2025-24928h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated