Top issues
Detected presence of software components that can tamper with the system security settings.
hunting
Problem
Software components sometimes need to interact with higher privilege parts of the operating system, often requiring administrative access to accomplish a task. System security settings are the first line of defense against the most common attack vectors. For that reason, attackers often aim to tamper with system security settings. Disabling User Access Controls (UAC) and other security settings enables malicious code to execute without being blocked. While the presence of code that tampers with system security settings does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Only select applications should consider using functions that interact with system security settings. One example of acceptable use for such functions is allowing specialized applications to install as services that monitor the operating system events.Prevalence in PowerShell Gallery community
5 packages
found in
Top 100
87 packages
found in
Top 1k
724 packages
found in
Top 10k
1272 packages
in community
Next steps
Investigate reported detections as indicators of software tampering.
Consult Mitre ATT&CK documentation: T1562.001 - Disable or Modify Tools.
Consider rewriting the flagged code without using the marked behaviors.
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
389 packages
found in
Top 1k
1464 packages
found in
Top 10k
2513 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 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
8 packages
found in
Top 100
25 packages
found in
Top 1k
130 packages
found in
Top 10k
259 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
Tampers with Active Directory settings.
settings
Prevalence in PowerShell Gallery community
Behavior uncommon for this community (Uncommon)
1 packages
found in
Top 100
33 packages
found in
Top 1k
429 packages
found in
Top 10k
743 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
Contains URLs that link to raw files on GitHub.
network
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
7 packages
found in
Top 100
389 packages
found in
Top 1k
1465 packages
found in
Top 10k
2514 packages
in community
Changes preference variables to silent mode.
stealth
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
18 packages
found in
Top 100
384 packages
found in
Top 1k
3431 packages
found in
Top 10k
5814 packages
in community
Enumerates operating system information using WMI.
search
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
4 packages
found in
Top 100
56 packages
found in
Top 1k
269 packages
found in
Top 10k
459 packages
in community
Top vulnerabilities
No vulnerabilities found.