Top issues
Problem
Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.Prevalence in PowerShell Gallery community
13 packages
found in
Top 100
176 packages
found in
Top 1k
997 packages
found in
Top 10k
1.61k packages
in community
Next steps
Investigate reported detections.
If the software intent does not relate to the reported behavior, investigate your build and release environment for software supply chain compromise.
You should delay the software release until the investigation is completed, or until the issue is risk accepted.
Consider rewriting the flagged code without using the marked behaviors.
Problem
Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.Prevalence in PowerShell Gallery community
2 packages
found in
Top 100
22 packages
found in
Top 1k
836 packages
found in
Top 10k
2.54k packages
in community
Next steps
Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.
Top behaviors
Hides a window during execution of the code.
stealth
Prevalence in PowerShell Gallery community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
24 packages
found in
Top 1k
185 packages
found in
Top 10k
319 packages
in community
Tampers with installed applications.
settings
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
4 packages
found in
Top 100
54 packages
found in
Top 1k
328 packages
found in
Top 10k
518 packages
in community
Gets or sets the security protocol used by the ServicePoint objects.
settings
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
4 packages
found in
Top 100
92 packages
found in
Top 1k
653 packages
found in
Top 10k
1.08k packages
in community
Creates or changes item properties, such as registry keys.
settings
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
2 packages
found in
Top 100
80 packages
found in
Top 1k
445 packages
found in
Top 10k
710 packages
in community
Installs or removes Windows Store apps.
payload
Prevalence in PowerShell Gallery community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
5 packages
found in
Top 1k
60 packages
found in
Top 10k
98 packages
in community
Top vulnerabilities
No vulnerabilities found.