Top issues
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
100 packages
found in
Top 100
900 packages
found in
Top 1k
8992 packages
found in
Top 10k
17108 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 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.
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)
90 packages
found in
Top 100
509 packages
found in
Top 1k
3113 packages
found in
Top 10k
5185 packages
in community
Contains IP addresses.
network
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
97 packages
found in
Top 100
693 packages
found in
Top 1k
4437 packages
found in
Top 10k
7330 packages
in community
Contains URLs.
network
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
90 packages
found in
Top 100
516 packages
found in
Top 1k
2293 packages
found in
Top 10k
3528 packages
in community
Contains URLs with an unusual number of subdomains.
network
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
84 packages
found in
Top 100
284 packages
found in
Top 1k
681 packages
found in
Top 10k
1272 packages
in community
Contains URLs related to URL shortener services.
network
Prevalence in PowerShell Gallery community
Behavior often found in this community (Common)
88 packages
found in
Top 100
346 packages
found in
Top 1k
1005 packages
found in
Top 10k
1856 packages
in community
Top vulnerabilities
No vulnerabilities found.