Top issues
Problem
Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. One or more embedded URLs were discovered to link to raw files hosted on GitHub. Attackers often abuse popular web services to host malicious payloads. Since code-sharing services URLs are typically allowed by security solutions, using them for payload delivery increases the odds that the malicious code will reach the user. While the presence of code-sharing service locations does not imply malicious intent, all of their uses in a software package should be documented and approved. An increasing number of software supply chain attacks in the open source space leverages the GitHub service to deliver malicious payloads.Prevalence in PowerShell Gallery community
7 packages
found in
Top 100
387 packages
found in
Top 1k
1476 packages
found in
Top 10k
2.58k packages
in community
Next steps
Investigate reported detections.
If the software should not include these network references, 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 an alternative delivery mechanism for software packages.
Detected presence of software components that have low popularity or number of downloads.
hunting
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. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community, it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of being the first to try out a new project lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.Prevalence in PowerShell Gallery community
1 packages
found in
Top 100
2 packages
found in
Top 1k
6 packages
found in
Top 10k
18 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.
Detected presence of software components that are rarely included by other public software packages.
hunting
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. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community. it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of using components that are rarely used to build applications lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.Prevalence in PowerShell Gallery community
1 packages
found in
Top 100
4 packages
found in
Top 1k
5 packages
found in
Top 10k
20 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
Loads additional snap-ins or modules to the current session.
payload
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
91 packages
found in
Top 100
509 packages
found in
Top 1k
3132 packages
found in
Top 10k
5.29k packages
in community
Imports values from .PSD1 file.
file
Prevalence in PowerShell Gallery community
Behavior uncommon for this community (Uncommon)
1 packages
found in
Top 100
43 packages
found in
Top 1k
330 packages
found in
Top 10k
606 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
6511 packages
found in
Top 10k
11.95k packages
in community
Evaluates code dynamically.
execution
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
55 packages
found in
Top 100
452 packages
found in
Top 1k
2955 packages
found in
Top 10k
4.69k packages
in community
Downloads or installs modules from remote repositories.
execution
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
7 packages
found in
Top 100
152 packages
found in
Top 1k
1494 packages
found in
Top 10k
2.56k packages
in community
Top vulnerabilities
No vulnerabilities found.