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 NuGet community
0 packages
found in
Top 100
22 packages
found in
Top 1k
142 packages
found in
Top 10k
59.57k 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 Windows executable files that embed PDB files whose integrity is verified with an insecure hashing algorithm.
Causes risk: outdated toolchains detected
hardening
Problem
Program database (PDB) files are typically only used during software development. They contain private debug symbols that make it significantly easier to reverse engineer a closed-source application. In some cases, having a program database file is equivalent to having access to the source code. Presence of program databases could indicate that one or more software components have been built using a debug profile, instead of the release.Prevalence in NuGet community
0 packages
found in
Top 100
14 packages
found in
Top 1k
69 packages
found in
Top 10k
19.61k packages
in community
Next steps
Private debug database files should not be embedded within executables, and you should remove them from the software package before releasing it.
The integrity verification of the embedded database files should not be done with insecure hashing algorithms. SHA1 and MD5 hashes should be deprecated throughout the application, and a more secure SHA256 algorithm should be used instead.
Detected presence of private debug database files.
Causes risk: debugging symbols found
secrets
Problem
Program database (PDB) files are typically only used during software development. They contain private debug symbols that make it significantly easier to reverse engineer a closed source application. In some cases, having a program database file is equivalent to having access to the source code. Presence of program databases could indicate that one or more software components have been built using a debug profile, instead of the release.Prevalence in NuGet community
0 packages
found in
Top 100
17 packages
found in
Top 1k
138 packages
found in
Top 10k
30.6k packages
in community
Next steps
Remove private debug database files from the software package before you release it.
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 NuGet community
No prevalence information at this timeNext 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 NuGet community
0 packages
found in
Top 100
38 packages
found in
Top 1k
315 packages
found in
Top 10k
733.24k 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
Retrieves the name of the user associated with the process.
search
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
4 packages
found in
Top 1k
70 packages
found in
Top 10k
23.06k packages
in community
Contains URIs related to Symantec security products.
network
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
62 packages
found in
Top 1k
484 packages
found in
Top 10k
560.29k packages
in community
Deletes files in Windows system directories.
file
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
3 packages
found in
Top 1k
48 packages
found in
Top 10k
10.35k packages
in community
Encodes data using the Base64 algorithm.
packer
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
21 packages
found in
Top 1k
144 packages
found in
Top 10k
69.16k packages
in community
Decodes data using the Base64 algorithm.
packer
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
21 packages
found in
Top 1k
133 packages
found in
Top 10k
60.64k packages
in community
Top vulnerabilities
No vulnerabilities found.