Skip to main content

SQ34251

Detected presence of commonly distributed service tokens.

priorityCI/CD statusseverityeffortRL levelRL assessment
NonepasslowlowNoneNone

About the issue​

Service access tokens are considered sensitive information that should not be included in released software packages. However, developers frequently release sensitive information alongside their applications to facilitate automated software testing. Testing tokens and keys often proliferate through the software supply chain. Any publicly documented testing keys or service access tokens can safely be ignored. List of such commonly distributed sensitive information is automatically updated and requires no additional user actions.

How to resolve the issue​

  • Review the commonly shared sensitive information for evidence of inadvertently exposed secrets.
  • If the tokens were published unintentionally and the software has been made public, you should revoke the tokens and file a security incident.

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

Secrets breakdown by service​

The next chart provides a more detailed look at sensitive information detected in analyzed packages. Secrets are grouped by service, and for every service the chart shows the absolute number of secrets found per repository.

When present in the chart, the "Other" group covers the following:

  • SWT Generic
  • RFC6750 Token
  • OAuth token credentials
  • Connection string with an exposed secret
  • Basic Access credentials
  • JWT Generic

Secrets breakdown for SQ34251