LoFP / false positives should be limited as this is specific to a file attribute not used by anything else. filter as needed.

Techniques

• T1069
• T1069.001
• T1069.002
• T1087
• T1087.001
• T1087.002
• T1482

Sample rules

Detect SharpHound Usage

• source: splunk
• technicques:
  • T1087.002
  • T1069.001
  • T1482
  • T1087.001
  • T1087
  • T1069.002
  • T1069

Description

The following analytic identifies SharpHound binary usage by using the original filena,e. In addition to renaming the PE, other coverage is available to detect command-line arguments. This particular analytic looks for the original_file_name of SharpHound.exe and the process name. It is possible older instances of SharpHound.exe have different original filenames. Dependent upon the operator, the code may be re-compiled and the attributes removed or changed to anything else. During triage, review the metadata of the binary in question. Review parallel processes for suspicious behavior. Identify the source of this binary.

Detection logic

| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where (Processes.process_name=sharphound.exe OR Processes.original_file_name=SharpHound.exe) by Processes.dest Processes.user Processes.parent_process_name Processes.original_file_name Processes.process_name Processes.process Processes.process_id Processes.parent_process_id 
| `drop_dm_object_name(Processes)` 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `detect_sharphound_usage_filter`