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
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 digital signatures that rely on a weak digest algorithm for integrity validation.
signatures
Problem
Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures verify the origin and the integrity of the object they apply to. The integrity validation relies on the cryptographic strength of the encryption and the hash verification algorithm. If either of the two is considered weak by current standards, there is a chance the signed object could be maliciously modified, without triggering the integrity failure check.Prevalence in PowerShell Gallery community
85 packages
found in
Top 100
354 packages
found in
Top 1k
1054 packages
found in
Top 10k
1674 packages
in community
Next steps
Create signatures with strong ECC key-length of at least 224 bits, or RSA key-length of at least 2048 bits, and use SHA256 as the hashing algorithm. While encryption key-length upgrade does require you to obtain a new certificate, the hashing algorithm can freely be selected during signing.
With Microsoft SignTool, you can specify the hashing algorithm using the /fd SHA256 parameter.
Detected digital signatures that have not been performed with an extended validation certificate.
signatures
Problem
Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures are made using digital certificates, which can either be purchased from certificate authorities or be self-issued. When a certificate is purchased from a certificate authority, the subject that requests it goes through an identity validation process. Depending on the certificate type, those checks can be basic or extended. Confirming the subject identity is a multi-step process, and the requesting subject can be mapped to its legal entity name only through extended validation of submitted documents. Extended identity validation typically costs more, and it takes longer for a certificate to be issued when this process is correctly followed.Prevalence in PowerShell Gallery community
86 packages
found in
Top 100
259 packages
found in
Top 1k
991 packages
found in
Top 10k
1561 packages
in community
Next steps
Consider the benefits of acquiring extended validation certificates. Operating systems tend to be more trusting of software packages signed in this way. Certain security warnings and prompts might also be automatically suppressed. This reduces the number of support tickets for organizations that opt to use extended validation certificates.
Top behaviors
Retrieves the name of the user associated with the process.
search
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
12 packages
found in
Top 100
172 packages
found in
Top 1k
803 packages
found in
Top 10k
1281 packages
in community
Encodes data using the Base64 algorithm.
packer
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
74 packages
found in
Top 100
404 packages
found in
Top 1k
2154 packages
found in
Top 10k
3540 packages
in community
Decodes data using the Base64 algorithm.
packer
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
68 packages
found in
Top 100
371 packages
found in
Top 1k
1732 packages
found in
Top 10k
2838 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
Executes a file.
execution
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
17 packages
found in
Top 100
283 packages
found in
Top 1k
1860 packages
found in
Top 10k
3073 packages
in community
Top vulnerabilities
No vulnerabilities found.