You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: triage.md
+61-6Lines changed: 61 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -7,11 +7,66 @@ title: Triage Analysis
7
7
8
8
# Section 4: Triage Analysis #
9
9
10
-
* Simple Search
11
-
* Collect Strings
12
-
* Check AV vendors
13
-
* Get basic PE information
14
-
* Run it in a VM
15
-
* Capture network information
10
+
Depending on your workload, you want to spend the least amount of time trying to determine what the malware is doing and how to get rid of it. Many malware analysts use their own triage analysis, similar to that in the Emergency Room at the hospital.
11
+
12
+
You will want to quickly narrow down specific information and indicators before moving on to deeper static and dynamic analysis.
13
+
14
+
This checklist should get you started:
15
+
-[ ] File Context and Delivery
16
+
-[ ] File Information & Header Analysis
17
+
-[ ] Get Basic PE information
18
+
-[ ] Simple Search
19
+
-[ ] Collect Strings
20
+
-[ ] Check AV vendors
21
+
-[ ] Quick VM Detonation
22
+
-[ ] Capture network information
23
+
24
+
###File Context and Delivery
25
+
26
+
When you receive the malware binary, it's important to ask how the malware got there in the first place.
27
+
28
+
Questions to ask:
29
+
* Did it come from an email?
30
+
* Did it come from a browser download?
31
+
* Was it quarantined in an Anti-Virus?
32
+
* Is it an anomalous process running?
33
+
34
+
###File Information & Header Analysis
35
+
36
+
* Use a **file** command (sniffer VM) to determine the file type
37
+
* Verify the file header using a hex editor (HxD)
38
+
39
+
###Get Basic PE information
40
+
41
+
* Parse the PE header using the tool CFF Explorer
42
+
* Determine what resources, DLL imports, and libraries used
43
+
* Example: If you see **Ws2_32.dll** it might be setting up a network connection because it's used for setting up sockets
44
+
45
+
###Simple Search
46
+
47
+
* Calculate the hash of the file an check the web to see if it's been seen already
48
+
49
+
###Collect Strings
50
+
51
+
* using the string command in linux or BinText tool, extract the strings to find any clues
52
+
53
+
###Check AV vendors
54
+
55
+
* Run the file against an Anti-Virus or VirusTotal to see if there are any detections
56
+
57
+
###Quick VM Detonation
58
+
59
+
* Use open source VM detonation services like hybrid-analysis.com or malwr.com to get the behavior quickly
60
+
61
+
###Capture network information
62
+
63
+
* Use the VM detonation service to capture any network connections or packet data.
64
+
* If you can't do this then we will need to dynamically debug the malware.
65
+
66
+
## Malware Analysis Report
67
+
68
+
You will want to capture this information throughout your investigation either through notes or report documents.
69
+
You can use the **Malware Analysis Report** template [HERE](https://securedorg.github.io/ReportForm.html)
0 commit comments