Spectra Assure
Community
Docs
warningRisk: Hardening
Scanned: 8 days ago

sign

latest
Top 10k
Sign CLI
License: Permissive (MIT)
Published: 3 months ago
See on NuGet

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
5 debugging symbols found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
5 outdated toolchains detected

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

Popularity

1.07M
Total Downloads
3
Contributors
0
Declared Dependencies
0
Dependents

Top issues

See all issues

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
19607 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.

Problem

Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.

Prevalence in NuGet community

0 packages
found in
Top 100
0 packages
found in
Top 1k
4 packages
found in
Top 10k
1095 packages
in community

Next steps

Investigate reported detections.
If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

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 NuGet community

No prevalence information at this time

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.

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
733240 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.

Problem

Debug databases are typically only used during software development. On Windows, they are usually files embedded into the executable (PDB), while on Linux, they're contained inside special executable sections. The databases contain private debug symbols that make it significantly easier to reverse-engineer a closed-source application. In some cases, having a debug database is equivalent to having access to the source code. Presence of debug databases could indicate that one or more software components have been built using a debug profile, instead of the release. Private debug databases can be embedded into software components by programming language tools.

Prevalence in NuGet community

0 packages
found in
Top 100
15 packages
found in
Top 1k
76 packages
found in
Top 10k
21579 packages
in community

Next steps

To remediate this issue and remove private debugging information, refer to your programming language toolchain documentation.

Top behaviors

See all behaviors

Prevalence in NuGet community

Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
6 packages
found in
Top 10k
1234 packages
in community

Prevalence in NuGet community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
4 packages
found in
Top 10k
133 packages
in community

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
23059 packages
in community

Prevalence in NuGet community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
1 packages
found in
Top 1k
24 packages
found in
Top 10k
6811 packages
in community

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
10351 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for sign

What is sign?

Sign CLI. For more information about this package, visit its homepage.

Is sign malicious or is it safe to use?

The .NET package sign was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is sign popular?

The .NET package sign ranks among the top 10000 projects in this community. It has 1M recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure sign once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how sign behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a sign version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.