Try in Splunk Security Cloud


This search is to detect an anomaly event of a non-firefox process accessing the files in the profile folder. This folder contains all the sqlite database of the firefox browser related to users login, history, cookies and etc. Most of the RAT, trojan spy as well as FIN7 jssloader try to parse the those sqlite database to collect information on the compromised host. This SACL Event (4663) needs to be enabled to the firefox profile directory to use this. Since this is monitoring the access to the folder, we have obsevered noise and hence added sqlite db browser and explorer.exe to make this detection more stable.

  • Type: Anomaly
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2024-04-26
  • Author: Teoderick Contreras, Splunk
  • ID: e6fc13b0-1609-11ec-b533-acde48001122




ID Technique Tactic
T1555 Credentials from Password Stores Credential Access
T1555.003 Credentials from Web Browsers Credential Access
Kill Chain Phase
  • Exploitation
  • DE.AE
  • CIS 10
`wineventlog_security` EventCode=4663 NOT (ProcessName IN ("*\\firefox.exe", "*\\explorer.exe", "*sql*")) ObjectName="*\\AppData\\Roaming\\Mozilla\\Firefox\\Profiles*" 
| stats count min(_time) as firstTime max(_time) as lastTime by ObjectName ObjectType ProcessName AccessMask EventCode dest 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `non_firefox_process_access_firefox_profile_dir_filter`


The SPL above uses the following Macros:

:information_source: non_firefox_process_access_firefox_profile_dir_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • _time
  • Object_Name
  • Object_Type
  • process_name
  • Access_Mask
  • Accesses
  • process_id
  • EventCode
  • dest
  • user

How To Implement

To successfully implement this search, you must ingest Windows Security Event logs and track event code 4663. For 4663, enable "Audit Object Access" in Group Policy. Then check the two boxes listed for both "Success" and "Failure."

Known False Positives

other browser not listed related to firefox may catch by this rule.

Associated Analytic Story


Risk Score Impact Confidence Message
35.0 50 70 a non firefox browser process $ProcessName$ accessing $ObjectName$

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.


Test Dataset

Replay any dataset to Splunk Enterprise by using our tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 2