|
2 | 2 |
|
3 | 3 | ## Windows
|
4 | 4 |
|
| 5 | +### Crawling the Registry Hive |
| 6 | + |
5 | 7 | On Windows, most configuration can be done through the *Registry Hive* –
|
6 | 8 | some kind of database that contains every configuration option about either the
|
7 | 9 | operating system itself, or any software that would like to store information
|
@@ -29,4 +31,23 @@ virtualBoxKeys := []string{
|
29 | 31 | `HKLM\SYSTEM\ControlSet001\Services\VBoxSF`,
|
30 | 32 | `HKLM\SYSTEM\ControlSet001\Services\VBoxVideo`,
|
31 | 33 | }
|
| 34 | +``` |
| 35 | + |
| 36 | +### Looking for known files |
| 37 | + |
| 38 | +Following a similar principle to the registries analysis, we can take a look to |
| 39 | +the file system, searching for particular files. When installed, the |
| 40 | +aforementioned *guest addons* add some files to the disk. These files are known |
| 41 | +and pretty easy to guess. A lot of malwares will would take a look at these. |
| 42 | +Here is a quick example: |
| 43 | + |
| 44 | +```golang |
| 45 | +vmwarePath := []string{ |
| 46 | + `c:\windows\system32\drivers\vmmouse.sys`, |
| 47 | + `c:\windows\system32\drivers\vmnet.sys`, |
| 48 | + `c:\windows\system32\drivers\vmxnet.sys`, |
| 49 | + `c:\windows\system32\drivers\vmhgfs.sys`, |
| 50 | + `c:\windows\system32\drivers\vmx86.sys`, |
| 51 | + `c:\windows\system32\drivers\hgfs.sys` |
| 52 | +} |
32 | 53 | ```
|
0 commit comments