
Two colors are used to indicate the executed path. The red dash lines show the non-executed path,
and the blue solid lines show the executed path.
According to the preceding control graph, the subroutine (Sub_004017A0) at virtual address
0x004017A0 was executed and is shown with a blue solid line pointing to the Sub_004017A0 box.
However, the subroutine (GetVersion]) was not called potentially as there is a red dash line pointing to
it.
The Sub_004017A0 subroutine is making 11 calls as there are 11 lines coming out of this box. Seven
of these 11 calls were executed during dynamic analysis. One of them is calling Sub_00401780 as
there is a blue solid line pointing from Sub_004017A0 to Sub_00401780. Calls to Sub_00401410,
printf, Sub_00401882, and Sub_00401320 were not executed and shown with red dashed line pointing
at them.
The Sub_00401780 subroutine is making only one unique call as there is only one line coming out
from this box. This call was executed during dynamic analysis.
User API Log
The User API Logs are contained in various files.
• The .log file contains the Windows user-level DLL API calls made directly by the analyzed file during
dynamic analysis. To view this file in the McAfee Advanced Threat Defense web application, select
Analysis | Analysis Results. Then click and select User API Log. Alternatively, click , select Complete
Results. Download the <sample_name>.zip file. This .zip file contains the same information in the
<sample name>.log file in the AnalysisLog folder. The content of the .log file includes the following:
• A record of all systems DLL API calling sequence.
• An address which indicates the approximate calling address where the DLL API call was made.
• Optional input and output parameters, and return code for key systems DLL API calls.
• The following are the other files containing the dynamic execution logs. All these files are contained
in the <sample name>.zip file.
• <sample name>ntv.txt file. This file contains the Windows Zw version of native system services
API calling sequence during the dynamic analysis. The API name typically starts with Zw as in
ZwCreateFile.
• log.zip
• dump.zip
• dropfiles.zip
• networkdrive.zip
Download the complete results .zip file
McAfee Advanced Threat Defense produces detailed analysis for each submitted sample. All the
available reports for an analyzed sample are available in a .zip file, which you can download from the
McAfee Advanced Threat Defense web application.
Task
1
Select Analysis | Analysis Results.
2
In the Analysis Results page, click
and select Complete Results .
Download the <sample_name>.zip file to the location you want. This .zip file contains the reports
for each analysis. The files in this .zip file are created and stored with a standard naming
7
Analyzing malware
View the analysis results
116
McAfee Advanced Threat Defense 3.0.4 Product Guide
Comentarios a estos manuales