joyce8 commited on
Commit
3d23efe
·
verified ·
1 Parent(s): e90225a

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +10 -6
README.md CHANGED
@@ -37,7 +37,7 @@ EMBER also includes features and labels for 6,315 malicious files in a "challeng
37
 
38
  The previous EMBER feature versions were pinned to [LIEF](lief.re) version 0.9.0, which requires Python 3.6. EMBER feature version 3 ("thrember") is a re-implementation of the EMBER feature vector format that uses the [pefile](https://github.com/erocarrera/pefile) library instead. pefile is stable and has no dependencies, making it ideal going forward. We have also made several addition to the EMBER feature vector format, which now includes features from the DOS header, Rich header, PE data directories, Authenticode signatures, and warnings during PE parsing. Furthermore, we have added support for feature extraction from non-PE files using a subset of the EMBER feature version 3 format. We show that effective classifiers for APK, ELF, and PDF files can be trained using just features from general file info, byte statistics, and string statistics.
39
 
40
- # Capa
41
 
42
  [Capa](https://github.com/mandiant/capa) is a malware analysis tool that identifies a file's potential behaviors. For each file, it outputs Mitre ATT&CK techniques, objectives and behaviors from the Malware Behavior Catalogue Matrix, and other capabilities. An example is shown below.
43
 
@@ -83,22 +83,26 @@ The previous EMBER feature versions were pinned to [LIEF](lief.re) version 0.9.0
83
  EMBER2024 has been updated to include Capa results for Win32, Win64, .NET, and ELF files.
84
 
85
  ```
86
- "caps": [
 
87
  {"Capability": "Find process by name", "Namespace": "host-interaction/process/list", "Addrs": []},
88
  {"Capability": "Terminate process", "Namespace": "host-interaction/process/terminate", "Addrs": ["0x6000025"]},
89
  {"Capability": "Move file", "Namespace": "host-interaction/file-system/move", "Addrs": []},
90
  ...
91
- ]
92
- "ttps": [
93
  {"Tactic": "DISCOVERY", "Technique": "Process Discovery [T1057]"},
94
  {"Tactic": "DISCOVERY", "Technique": "File and Directory Discovery [T1083]"}
95
- ],
96
- "mbc": [
97
  {"Objective": "OPERATING SYSTEM", "Behavior": "Console [C0033]"},
98
  {"Objective": "PROCESS", "Behavior": "Terminate Process [C0018]"},
99
  {"Objective": "FILE SYSTEM", "Behavior": "Move File [C0063]"},
100
  {"Objective": "DISCOVERY", "Behavior": "File and Directory Discovery [E1083]"},
101
  ....
 
 
 
102
  ```
103
 
104
  In many cases, Capa identifies the function(s) that the capability is present in. We created a [supplemental dataset](https://huggingface.co/datasets/joyce8/EMBER2024-capa) with the raw bytes and disassembly of 16,356,790 functions from malicious files in EMBER2024.
 
37
 
38
  The previous EMBER feature versions were pinned to [LIEF](lief.re) version 0.9.0, which requires Python 3.6. EMBER feature version 3 ("thrember") is a re-implementation of the EMBER feature vector format that uses the [pefile](https://github.com/erocarrera/pefile) library instead. pefile is stable and has no dependencies, making it ideal going forward. We have also made several addition to the EMBER feature vector format, which now includes features from the DOS header, Rich header, PE data directories, Authenticode signatures, and warnings during PE parsing. Furthermore, we have added support for feature extraction from non-PE files using a subset of the EMBER feature version 3 format. We show that effective classifiers for APK, ELF, and PDF files can be trained using just features from general file info, byte statistics, and string statistics.
39
 
40
+ ## Capa
41
 
42
  [Capa](https://github.com/mandiant/capa) is a malware analysis tool that identifies a file's potential behaviors. For each file, it outputs Mitre ATT&CK techniques, objectives and behaviors from the Malware Behavior Catalogue Matrix, and other capabilities. An example is shown below.
43
 
 
83
  EMBER2024 has been updated to include Capa results for Win32, Win64, .NET, and ELF files.
84
 
85
  ```
86
+ {
87
+ "caps": [
88
  {"Capability": "Find process by name", "Namespace": "host-interaction/process/list", "Addrs": []},
89
  {"Capability": "Terminate process", "Namespace": "host-interaction/process/terminate", "Addrs": ["0x6000025"]},
90
  {"Capability": "Move file", "Namespace": "host-interaction/file-system/move", "Addrs": []},
91
  ...
92
+ ],
93
+ "ttps": [
94
  {"Tactic": "DISCOVERY", "Technique": "Process Discovery [T1057]"},
95
  {"Tactic": "DISCOVERY", "Technique": "File and Directory Discovery [T1083]"}
96
+ ],
97
+ "mbc": [
98
  {"Objective": "OPERATING SYSTEM", "Behavior": "Console [C0033]"},
99
  {"Objective": "PROCESS", "Behavior": "Terminate Process [C0018]"},
100
  {"Objective": "FILE SYSTEM", "Behavior": "Move File [C0063]"},
101
  {"Objective": "DISCOVERY", "Behavior": "File and Directory Discovery [E1083]"},
102
  ....
103
+ ],
104
+ ...
105
+ }
106
  ```
107
 
108
  In many cases, Capa identifies the function(s) that the capability is present in. We created a [supplemental dataset](https://huggingface.co/datasets/joyce8/EMBER2024-capa) with the raw bytes and disassembly of 16,356,790 functions from malicious files in EMBER2024.