Malware Scanner
Last updated
Last updated
A compromised software supply chain can result in alterations to the software, potentially serving as a vector for malware distribution. Allowing malicious actors to introduce harmful code, unintended behaviors and backdoors.
Malicious Code Evidence consists of indicators of malicious software (malware) identified through static analysis of the target software. Analyzing software for potential supply chain vulnerabilities complements software security reviews with automation. Adversaries often employ obfuscation techniques to conceal their alterations from human review, but these methods can also provide evidence of their behaviour. See ()
Based on the collected evidence, a maliciousness score
is calculated for the software being analyzed. If sufficient evidence is gathered, the software may be classified as potentially malicious.
The Malware Scanner is a tool that analyzes software project files and reports the evidence detected by the active malware policies assigned to the project. Detected evidence can be uploaded to Xygeni platform for consolidation and for enabling response actions.
Use the following command to run and upload the results of the Malware Scan to the Xygeni Platform. This command will scan the current directory for the target project.
Export malware evidence with critical severity to CSV for review or to import findings into other tools:
Use the xygeni malware [options]
command to execute the Malware Scanner.
To view all available options, use the --help
flag:
The most important properties are:
Name of the Xygeni Project -n
or --name
.
Input source to analyze. Either specify a directory with: -d
or --dir
or specify a repository using: --repo
. The scan will analyze the current working directory when no target is specified.
Upload results to the service --upload
. By default, results are not uploaded.
Output file (-o
or --output
) and format (-f
or --format
). If no output file is specified (or stdout / - are used), the standard output is used. Use --format=none
for no output.
Specify what detectors to run with the --detectors
/ --skip-detectors
options. A common use-case is to consider only issues with high or critical severity with --detectors=high
.
The resource kinds to be scanned could also be tailored with the --kinds
/ --skip-kinds
options.
Please refer to the documentation for information regarding this topic.