Skip to main content

SQ34403

Detected presence of active webhook service access keys.

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

About the issue​

Software as a Service (SaaS) platforms expose programmable interfaces for action automation and secure exchange of information. Webhooks are web callback interfaces that enable real-time event notifications. Applications provide a public-facing interface that the web service calls when a specific event occurs. Authentication is done by the application that the web service accesses through a secret key. Since the key is encoded in the webhook callback, the service interface parameters should never be included in a software release package, even if they are obfuscated by encryption on the client-side. For supported web services, webhooks are automatically validated via the least privilege APIs the service exposes. Detected webhooks 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.

How to resolve the issue​

  • If webhook keys were published unintentionally and the software has been made public, you should revoke the exposed webhook secrets and file a security incident.
  • Examples of webhook secrets that may have been detected include AWS, Slack, Office365 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).