Network Logon Provider Registry Modification
Identifies the modification of the network logon provider registry. Adversaries may register a rogue network logon provider module for persistence and/or credential access via intercepting the authentication credentials in clear text during user logon.
Elastic rule (View on GitHub)
1[metadata]
2creation_date = "2021/03/18"
3integration = ["endpoint", "m365_defender", "windows"]
4maturity = "production"
5updated_date = "2026/09/18"
6[transform]
7[[transform.osquery]]
8label = "Osquery - Retrieve DNS Cache"
9query = "SELECT * FROM dns_cache"
10
11[[transform.osquery]]
12label = "Osquery - Retrieve All Services"
13query = "SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services"
14
15[[transform.osquery]]
16label = "Osquery - Retrieve Services Running on User Accounts"
17query = """
18SELECT description, display_name, name, path, pid, service_type, start_type, status, user_account FROM services WHERE
19NOT (user_account LIKE '%LocalSystem' OR user_account LIKE '%LocalService' OR user_account LIKE '%NetworkService' OR
20user_account == null)
21"""
22
23[[transform.osquery]]
24label = "Osquery - Retrieve Service Unsigned Executables with Virustotal Link"
25query = """
26SELECT concat('https://www.virustotal.com/gui/file/', sha1) AS VtLink, name, description, start_type, status, pid,
27services.path FROM services JOIN authenticode ON services.path = authenticode.path OR services.module_path =
28authenticode.path JOIN hash ON services.path = hash.path WHERE authenticode.result != 'trusted'
29"""
30
31
32[rule]
33author = ["Elastic"]
34description = """
35Identifies the modification of the network logon provider registry. Adversaries may register a rogue network logon
36provider module for persistence and/or credential access via intercepting the authentication credentials in clear text
37during user logon.
38"""
39false_positives = ["Authorized third party network logon providers."]
40from = "now-9m"
41index = [
42 "logs-endpoint.events.registry-*",
43 "endgame-*",
44 "logs-windows.sysmon_operational-*",
45 "winlogbeat-*",
46 "logs-m365_defender.event-*",
47]
48language = "eql"
49license = "Elastic License v2"
50name = "Network Logon Provider Registry Modification"
51note = """## Triage and analysis
52
53### Investigating Network Logon Provider Registry Modification
54
55Network logon providers are components in Windows responsible for handling the authentication process during a network logon.
56
57This rule identifies the modification of the network logon provider registry. Adversaries may register a rogue network logon provider module for persistence and/or credential access via intercepting the authentication credentials in plain text during user logon.
58
59> **Note**:
60> This investigation guide uses the [Osquery Markdown Plugin](https://www.elastic.co/guide/en/security/current/invest-guide-run-osquery.html) introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
61
62### Possible investigation steps
63
64- Examine the `registry.data.strings` field to identify the DLL registered.
65- Identify the process responsible for the registry operation and the file creation and investigate their process execution chains (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
66 - Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
67 - Investigate any abnormal behavior by the subject process, such as network connections, DLLs loaded, registry or file modifications, and any spawned child processes.
68- Retrieve the file and examine if it is signed with valid digital signatures from vendors that are supposed to implement this kind of software and approved to use in the environment. Check for prevalence in the environment and whether they are located in expected locations.
69- Investigate other alerts associated with the user/host during the past 48 hours.
70- Examine the host for derived artifacts that indicate suspicious activities:
71 - Analyze the executables of the processes using a private sandboxed analysis system.
72 - Observe and collect information about the following activities in both the sandbox and the alert subject host:
73 - Attempts to contact external domains and addresses.
74 - Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's `process.entity_id`.
75 - Examine the DNS cache for suspicious or anomalous entries.
76 - $osquery_0
77 - Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
78 - Examine the host services for suspicious or anomalous entries.
79 - $osquery_1
80 - $osquery_2
81 - $osquery_3
82 - Retrieve the files' SHA-256 hash values using the PowerShell `Get-FileHash` cmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
83
84
85### False positive analysis
86
87- False Positives can include legitimate software installations or updates that modify the network logon provider registry. These modifications may be necessary for the proper functioning of the software and are not indicative of malicious activity.
88
89### Response and Remediation
90
91- Initiate the incident response process based on the outcome of the triage.
92 - If malicious activity is confirmed, perform a broader investigation to identify the scope of the compromise and determine the appropriate remediation steps.
93- Isolate the involved host to prevent further post-compromise behavior.
94- If the triage identified malware, search the environment for additional compromised hosts.
95 - Implement temporary network rules, procedures, and segmentation to contain the malware.
96 - Stop suspicious processes.
97 - Immediately block the identified indicators of compromise (IoCs).
98 - Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
99- Remove and block malicious artifacts identified during triage.
100- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
101- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
102- Reimage the host operating system or restore the compromised files to clean versions.
103- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
104- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
105"""
106
107setup = """## Setup
108
109This rule is designed for data generated by [Elastic Defend](https://www.elastic.co/security/endpoint-security), which provides native endpoint detection and response, along with event enrichments designed to work with our detection rules.
110
111Setup instructions: https://ela.st/install-elastic-defend
112
113### Additional data sources
114
115This rule also supports the following third-party data sources. For setup instructions, refer to the links below:
116
117- [Microsoft Defender XDR](https://ela.st/m365-defender)
118- [Sysmon Registry Events](https://ela.st/sysmon-event-reg-setup)
119"""
120
121references = [
122 "https://github.com/gtworek/PSBits/tree/master/PasswordStealing/NPPSpy",
123 "https://docs.microsoft.com/en-us/windows/win32/api/npapi/nf-npapi-nplogonnotify",
124]
125risk_score = 47
126rule_id = "54c3d186-0461-4dc3-9b33-2dc5c7473936"
127severity = "medium"
128tags = [
129 "Domain: Endpoint",
130 "OS: Windows",
131 "Use Case: Threat Detection",
132 "Tactic: Persistence",
133 "Tactic: Credential Access",
134 "Data Source: Elastic Endgame",
135 "Data Source: Elastic Defend",
136 "Data Source: Sysmon",
137 "Data Source: Microsoft Defender XDR",
138 "Resources: Investigation Guide",
139 "Noise: Medium",
140 "Performance: Normal",
141 "Rule Type: Event Correlation (EQL)",
142 "Platform: Windows",
143 "Resources: Osquery",
144]
145timestamp_override = "event.ingested"
146type = "eql"
147
148query = '''
149registry where host.os.type == "windows" and event.type == "change" and
150 registry.data.strings : "?*" and registry.value : "ProviderPath" and
151 registry.path : (
152 "HKLM\\SYSTEM\\*ControlSet*\\Services\\*\\NetworkProvider\\ProviderPath",
153 "\\REGISTRY\\MACHINE\\SYSTEM\\*ControlSet*\\Services\\*\\NetworkProvider\\ProviderPath"
154 ) and
155 /* Excluding default NetworkProviders RDPNP, LanmanWorkstation and webclient. */
156 not (
157 user.id : "S-1-5-18" and
158 registry.data.strings : (
159 "%SystemRoot%\\System32\\ntlanman.dll",
160 "%SystemRoot%\\System32\\drprov.dll",
161 "%SystemRoot%\\System32\\davclnt.dll",
162 "%SystemRoot%\\System32\\vmhgfs.dll",
163 "?:\\Program Files (x86)\\Citrix\\ICA Client\\x64\\pnsson.dll",
164 "?:\\Program Files\\Dell\\SARemediation\\agent\\DellMgmtNP.dll",
165 "?:\\Program Files (x86)\\CheckPoint\\Endpoint Connect\\\\epcgina.dll"
166 )
167 )
168'''
169
170
171[[rule.threat]]
172framework = "MITRE ATT&CK"
173
174[[rule.threat.technique]]
175id = "T1556"
176name = "Modify Authentication Process"
177reference = "https://attack.mitre.org/techniques/T1556/"
178
179[[rule.threat.technique.subtechnique]]
180id = "T1556.008"
181name = "Network Provider DLL"
182reference = "https://attack.mitre.org/techniques/T1556/008/"
183
184[rule.threat.tactic]
185id = "TA0006"
186name = "Credential Access"
187reference = "https://attack.mitre.org/tactics/TA0006/"
188
189[[rule.threat]]
190framework = "MITRE ATT&CK"
191
192[[rule.threat.technique]]
193id = "T1543"
194name = "Create or Modify System Process"
195reference = "https://attack.mitre.org/techniques/T1543/"
196
197[rule.threat.tactic]
198id = "TA0003"
199name = "Persistence"
200reference = "https://attack.mitre.org/tactics/TA0003/"
Triage and analysis
Investigating Network Logon Provider Registry Modification
Network logon providers are components in Windows responsible for handling the authentication process during a network logon.
This rule identifies the modification of the network logon provider registry. Adversaries may register a rogue network logon provider module for persistence and/or credential access via intercepting the authentication credentials in plain text during user logon.
Note: This investigation guide uses the Osquery Markdown Plugin introduced in Elastic Stack version 8.5.0. Older Elastic Stack versions will display unrendered Markdown in this guide.
Possible investigation steps
- Examine the
registry.data.stringsfield to identify the DLL registered. - Identify the process responsible for the registry operation and the file creation and investigate their process execution chains (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
- Validate the activity is not related to planned patches, updates, network administrator activity, or legitimate software installations.
- Investigate any abnormal behavior by the subject process, such as network connections, DLLs loaded, registry or file modifications, and any spawned child processes.
- Retrieve the file and examine if it is signed with valid digital signatures from vendors that are supposed to implement this kind of software and approved to use in the environment. Check for prevalence in the environment and whether they are located in expected locations.
- Investigate other alerts associated with the user/host during the past 48 hours.
- Examine the host for derived artifacts that indicate suspicious activities:
- Analyze the executables of the processes using a private sandboxed analysis system.
- Observe and collect information about the following activities in both the sandbox and the alert subject host:
- Attempts to contact external domains and addresses.
- Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's
process.entity_id. - Examine the DNS cache for suspicious or anomalous entries.
- $osquery_0
- Use the Elastic Defend network events to determine domains and addresses contacted by the subject process by filtering by the process's
- Use the Elastic Defend registry events to examine registry keys accessed, modified, or created by the related processes in the process tree.
- Examine the host services for suspicious or anomalous entries.
- $osquery_1
- $osquery_2
- $osquery_3
- Attempts to contact external domains and addresses.
- Retrieve the files' SHA-256 hash values using the PowerShell
Get-FileHashcmdlet and search for the existence and reputation of the hashes in resources like VirusTotal, Hybrid-Analysis, CISCO Talos, Any.run, etc.
False positive analysis
- False Positives can include legitimate software installations or updates that modify the network logon provider registry. These modifications may be necessary for the proper functioning of the software and are not indicative of malicious activity.
Response and Remediation
- Initiate the incident response process based on the outcome of the triage.
- If malicious activity is confirmed, perform a broader investigation to identify the scope of the compromise and determine the appropriate remediation steps.
- Isolate the involved host to prevent further post-compromise behavior.
- If the triage identified malware, search the environment for additional compromised hosts.
- Implement temporary network rules, procedures, and segmentation to contain the malware.
- Stop suspicious processes.
- Immediately block the identified indicators of compromise (IoCs).
- Inspect the affected systems for additional malware backdoors like reverse shells, reverse proxies, or droppers that attackers could use to reinfect the system.
- Remove and block malicious artifacts identified during triage.
- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
- Run a full antimalware scan. This may reveal additional artifacts left in the system, persistence mechanisms, and malware components.
- Reimage the host operating system or restore the compromised files to clean versions.
- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
References
Related rules
- Adding Hidden File Attribute via Attrib
- Persistence via PowerShell profile
- Potential Persistence via Time Provider Modification
- Registry Persistence via AppInit DLL
- Browser Process Spawned from an Unusual Parent