Running IREC from command line

This section describes how to invoke IREC from commandline or remotely using tools such as PsExec.


Command line support is only available in TACTICAL Edition.

By default, IREC starts in GUI mode unless a command line option starting with a dash (-) is provided. Command line options come in two flavors: A long form such as --profile and a short form: -p. See the example below for providing evidence acquisition profile

IREC.exe --profile full
IREC.exe -p full

Command Line Options

--help / -h

Displays the URL for the latest documentation.

--no-wait / -nw

By default, IREC will wait for a key press once the requested operation completes. Providing this option will make it terminate immediately without waiting for a key press.


You should always provide this option when running IREC remotely using tools such as PsExec.


IREC.exe --profile full --no-wait
--license <Key> / -l <Key>

Provides the license key to use for activating IREC. If not provided, IREC will try to read the Key from License section of IREC.Settings.ini file.


IREC.exe --license AAA-BBB-CCC-DDD

--app-dir <FolderPath> / -ad <FolderPath>

By default, IREC uses the directory is executed from as its Application Directory. This option tells IREC to use the provided directory for creating/reading/writing the files and folders listed below:

  • IREC.Settings.ini: All application settings are saved into this file.
  • IREC.Log.txt: All application logs.
  • IREC.Error.txt: Only created when an exception occurs.
  • IREC.Rulesets: Folder for Custom Content Profiles (.ccp files).
  • IREC.Profiles: Folder for YARA scripts (.yar files).
  • IREC.Bin: Created by IREC Dongle Edition (a SFX archive) for extracting its contents.


By default, provided folder path will be used for saving case output as well. You can override this behaviour by providing either case-dir or output-dir options.


This option is required for performing Triage using a YARA Ruleset or collecting custom content when IREC is executed remotely via PsExec!


IREC.exe --app-dir "\\MACHINE\IREC-DIR"

IREC.exe -ad "\\MACHINE\IREC-DIR" --triage-ruleset MyYaraRules --triage-memory # Uses \\MACHINE\IREC-DIR\IREC.Rulesets\MyYaraRules-memory.yar file

IREC.exe -ad "\\MACHINE\IREC-DIR" --custom-content "Hacked Server"  # Uses \\MACHINE\IREC-DIR\IREC.Profiles\Hacked Server.cpp file
--profile <Profile> / -p <Profile>

Selects the Evidence Collection Profile. Can be one of the following:

  • full: Collects all evidence types.
  • custom: Each evidence type should be provided separately from command line. See Evidence Types for more information.
  • memory: Collects RAM and PageFile only.
  • default: Collects only default enabled evidence types.


Default selected profile is "Custom" which requires each evidence item to be separately provided from command line. See Evidence Types for more information.


IREC.exe --profile full

IREC.exe -p custom -ram -hbr -pf -evt -evtx
--output-dir <DirPath> / -od <DirPath>

Sets the directory in which case directory will be created in. Case directory is in format TIMESTAMP-MACHINENAME. If you want to provide an absolute path, use ---case-dir option instead. Trailing backslash is ignored.


IREC.exe --output-dir C:\Cases\Root

IREC.exe -od "C:\Case Folder\Root"
--case-dir <CasePath> / -cd <CasePath>

Sets the absolute path of case directory. Provided path will be used as is without creating any folders inside. If you want IREC to automatically create a directory for each case, use ---output-dir option instead. Trailing backslash is ignored.


IREC.exe --case-dir "C:\Cases\Final"

IREC.exe -cd "C:\Cases\Final"
--custom-content <ProfileName> / -cc <ProfileName>

Provides custom content collection profile name. Custom Content profiles can be found in IREC.Profiles folder in IREC.ProfileName.ccp format. IREC expects only the ProfileName portion in this command line option.


IREC.exe --custom-content "Hacked Server"

IREC.exe -cc SomeProfile
--triage-ruleset <RuleSetName> / -tr <RuleSetName>

Selects the provided rule set for performing Triage with YARA. If not provided, Default ruleset will be used in case memory or filesystem triage is enabled with either ---triage-memory or ---triage-filesystem options.


IREC.exe --triage-ruleset "New Set" --triage-memory

IREC.exe -tr Default -tm
--triage-memory / -tm

Enables memory triage. In case ---triage-ruleset is not provided, Default ruleset will be used.


IREC.exe --triage-memory

IREC.exe -tm
--triage-filesystem / -tf

Enables filesystem triage. In case ---triage-ruleset is not provided, Default ruleset will be used.


IREC.exe --triage-filesystem

IREC.exe -tf

Evidence Types

You can use the command line options for enabling each evidence type separately when Custom evidence collection profile is selected by providing --profile custom option.

Name Long Form Short Form Default
Clipboard --Clipboard -clp TRUE
Crash Dump Info --CrashDumpInfo -cdi TRUE
Recycle Bin Info --RecycleBinInfo -rbi TRUE
Restore Point Info --RestorePointInfo -rpi TRUE
Driver Info --DriverInfo -dri TRUE
Process Info --ProcessInfo -pri TRUE
Screenshots --Screenshots -scr TRUE
AntiVirus Info --AVInfo -avi TRUE
DNS Server --DNSServer -dnss TRUE
Proxy Info --ProxyInfo -prxy TRUE
Volume Info --VolumeInfo -voli TRUE
PageFile --PageFile -pgf TRUE
SwapFile --SwapFile -swp FALSE
Hibernation File --HibernationFile -hbr FALSE
Chrome History --ChromeHistory -chst TRUE
Firefox History --FirefoxHistory -fhst TRUE
IE History --InternetExplorerHistory -ihst TRUE
Edge History --EdgeHistory -ehst TRUE
MFT as CSV --MFTCsv -mftcsv TRUE
MFT as Binary --MFTBin -mft FALSE
MFT Mirror --MFTMirr -mftmir FALSE
Ntfs LogFile --NtfsLogFile -ntfslog TRUE
Ntfs UsnJournal --NtfsUsnJournal -usnjrn TRUE
Registry Hives --Hives -hiv TRUE
Registry Hives (Windows.Old) --HivesOld -hivold TRUE
DNS Cache --DNSCache -dnsc TRUE
TCP Table --TCPTable -tcpt TRUE
UDP Table --UDPTable -udpt TRUE
ARP Table --ARPTable -arpt TRUE
IPv4 Routes --IPv4Routes -ipv4 TRUE
Network Adapters --NetworkAdapters -netadp TRUE
Network Shares --NetworkShares -netshr TRUE
Hosts File --HostsFile -hosts TRUE
WMI Active Script --WMIActiveScript -wmiasc TRUE
WMI Command Line --WMICommandLine -wmicec TRUE
Prefetch --Prefetch -pf TRUE
ActivitiesDb --ActivitiesDb -adb TRUE
AmCache --AmCache -amc TRUE
RecentFileCache --RecentFileCache -rfc TRUE

Command Line Examples

Collecting all evidence types

IREC.exe --license AAAA-BBBB-CCDD-DDDD --profile full

Collecting RAM and Page File

IREC.exe --license AAAA-BBBB-CCDD-DDDD --profile memory

Collecting Custom Evidence (Chrome History, Event Logs, Clipboard)

IREC.exe --license AAAA-BBBB-CCDD-DDDD --profile custom -chst -evt -evtx -clp

Collecting Default Selected Evidence Types

IREC.exe --license AAAA-BBBB-CCDD-DDDD --profile default

Performing Memory Triage

IREC.exe --license AAAA-BBBB-CCDD-DDDD --triage-ruleset RuleSetName -tm

Performing FileSystem and Memory Triage

IREC.exe --license AAAA-BBBB-CCDD-DDDD --triage-ruleset RuleSetName -tm -tf

Collecting Full Evidence into a predefined case directory

IREC.exe --license AAAA-BBBB-CCDD-DDDD -p full --case-dir "C:\Some\Folder\Case"

Collecting Full Evidence into a predefined directory (a new folder will be created for each collection)

IREC.exe --license AAAA-BBBB-CCDD-DDDD -p full --output-dir "C:\Some\Folder"

Running IREC via PsExec

PsExec.exe \\ -u "WIN1064\John" -p "password" -h -n 60 -accepteula -c -f IREC.exe -l AAAA-BBBB-CCCC-DDDD -nw -p full -ad "\\NET\SHARE\IREC" -tr "MyYaraRules" -tm -cc "Hacked Server"