Skip to main content

SQ30205

Detected presence of software components with malicious dependencies.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
failhighhigh1malware: fail
Reason: malicious dependencies found

About the issue​

Proprietary ReversingLabs malware detection algorithms have determined that the software package has one or more malicious dependencies. Some software dependencies may be optional, and could be installed or downloaded only if a certain pre-defined condition is met. When software dependencies are confirmed to be found within the software package, additional issues might also be reported. The detection was made by either a static byte signature, software component identity, or a complete file hash. This malware detection method is considered highly accurate, and can typically attribute malware to previously discovered software supply chain attacks.

How to resolve the issue​

  • Inspect behaviors exhibited by the detected software components.
  • If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
  • Revise the use of components that raise these alarms. If you can't deprecate those components, make sure they are well-documented.
  • Avoid using this software package until it is vetted as safe.

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: 203K
  • Nuget: 735K
  • PyPi: 838K
  • NPM: 5.12M
  • VS Code: 113K
  • PS Gallery: 17K

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