# Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.

### AfterMidnight

# Assassin v1.4 Users Guide

1 June, 2014

- 1
- 2
…
- 151
- 152
- 153
- 154
- 155
…
- 203
- 204

SECRET//ORCON//NOFORN
18.2.4 Extractor Configuration
This section will describe the xml formats for all of the configuration values
contained under the <Extractor> XML tag. The extractor configuration is used for the
Injection Extractor. An example of a complete Extractor configuration is shown
below:
XML Configuration Example
<Extractor>
<Path32>c:\temp\launcher32.exe</Path32>
<Path64>c:\temp\launcher64.exe</Path64>
</Extractor>
Field Definitions
32-bit Launcher Path
The 32-bit launcher path is the path where the launcher will be copied to once
the Extractor runs. It will only be used if the Extractor is running on a 32-bit
system, and if the directories don’t exist, they will be created. However, during
uninstall; only the launcher file will be deleted, so it is recommended that a
directory that already exists on target is used
In the example above, the 32-bit launcher path will be copied to
“c:\temp\launcher32.exe”.
64-bit Launcher Path
The 64-bit launcher path is the path where the launcher will be copied to once
the Extractor runs. It will only be used if the Extractor is running on a 64-bit
system, and if the directories don’t exist, they will be created. However, during
uninstall; only the launcher file will be deleted, so it is recommended that a
directory that already exists on target is used.
In the example above, the 64-bit launcher path will be copied to
“c:\temp\launcher64.exe”.
153
SECRET//ORCON//NOFORN

- 1
- 2
…
- 151
- 152
- 153
- 154
- 155
…
- 203
- 204