Skip to main content

SQ20115

Detected digital signatures that are failing integrity validation check.

priorityCI/CD statusseverityeffortRL levelRL assessment
failhighmedium1tampering: fail
Reason: tampered signatures detected

About the issue​

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. Signatures contain a cryptographic hash of the object they are signing. Any mismatch between the expected and computed hashes is reported as an integrity validation failure. This can happen for a few reasons. Either the software package got damaged during network transport, or a post-signing process changed some of the package contents, or there was an attempt to tamper with the package. Discerning between these cases is impossible without manually inspecting the affected packages.

How to resolve the issue​

  • Inspect the software package for malicious software supply chain tampering.
  • If there is no evidence of tampering, re-sign and re-publish the software component.
  • If there are any post-signing processes that might modify the software package, move them to an earlier point in the release process.

Incidence statistics​

ReversingLabs periodically collects and analyzes the contents of popular software package repositories for threat research purposes.

For every repository, the chart shows the percentage of projects that triggered the software assurance policy. In other words, it shows how many projects were found to have the specific issue described on this page.

The percentages are calculated from the total amount of packages analyzed:

  • RubyGems: 174K
  • Nuget: 189K
  • PyPi: 403K
  • NPM: 2.1M