Skip to main content

SQ34401

Detected presence of active web service tokens.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
failhighmedium2secrets: fail
Reason: active web service credentials

About the issue​

Software as a Service (SaaS) platforms expose programmable interfaces to their authenticated users. These web services enable action automation and secure exchange of information. For authorization, users provide a unique token that confirms their access rights to the web service. Access tokens for supported web services are automatically validated via the least privilege APIs the service exposes. Detected tokens have been accepted as valid by the services they are associated with. This indicates they are currently active and may be abused if exposed to the public. Web service access tokens are considered secrets. They should never be included in a software release package, even if they are obfuscated by encryption on the client-side.

How to resolve the issue​

  • You should securely store web service access tokens, and fully automate their management and periodic rotation.
  • If tokens were published unintentionally and the software has been made public, you should revoke exposed tokens and file a security incident.
  • Examples of service tokens that may have been detected include AWS, Facebook, JWT, SWT, Slack and others.

Incidence statistics​

ReversingLabs periodically collects and analyzes the contents of popular software package repositories for threat research purposes. Analysis results are used to calculate incidence statistics for issues (policy violations) that Spectra Assure can detect in software packages.

This section is updated when new data becomes available.

Total amount of packages analyzed

  • RubyGems: 183K
  • Nuget: 644K
  • PyPi: 628K
  • NPM: 3.72M

Total detections per repository

For every repository, the chart shows the number of packages that triggered the software assurance policy. In other words, it shows how many packages in each package repository were found to have the specific issue described on this page. This information helps you understand how common the issue is across different software communities.

If a repository is absent from the chart, that means none of the packages in that repository triggered this policy during analysis, or the policy was not used during analysis.

Distribution of total detections by project popularity

For every repository, the chart shows how many of the total detections belong to the Top 100 (1-100), Top 1000 (101-1000) and Top 10 000 (1001-10 000) most downloaded projects. This information helps you understand the impact of the issue within each community, making it clearer when the issue affects the most popular projects.

If the chart shows zero values for all of the top project groups, that means all detections were in unranked projects (lower than 10 000 on the list of most downloaded projects).