Skip to main content

TH15103

Detected presence of files with behaviors commonly used by malicious software.

priorityCI/CD statusseverityeffortSAFE levelSAFE assessment
passmediumhighNoneNone

About the issue​

Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.

How to resolve the issue​

  • Investigate reported detections.
  • If the software intent does not relate to the reported behavior, investigate your build and release environment for software supply chain compromise.
  • You should delay the software release until the investigation is completed, or until the issue is risk accepted.
  • Consider rewriting the flagged code without using the marked behaviors.

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

Software behaviors that trigger the issue​

ReversingLabs periodically collects and analyzes the contents of popular software package repositories for threat research purposes. Software behaviors identified in collected and analyzed packages are assigned different prevalence tags.

Prevalence of a behavior illustrates how common that behavior is for a specific software community, or how often it has been found in software packages created in a specific programming language.

Behaviors that are often found in malicious packages are assigned the important tag. When Spectra Assure detects those behaviors in your software, this issue is triggered and displayed in analysis reports.

Behaviors per category

  • 17 important behaviors in the steal category
  • 4 important behaviors in the network category
  • 5 important behaviors in the stealth category
  • 5 important behaviors in the anomaly category
  • 51 important behaviors in the evasion category
  • 7 important behaviors in the execution category
  • 1 important behaviors in the macro category
  • 16 important behaviors in the file category
  • 2 important behaviors in the memory category
  • 3 important behaviors in the packer category
  • 2 important behaviors in the registry category
  • 4 important behaviors in the search category
  • 1 important behaviors in the monitor category