1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
//! Known-good Windows **service-binary** catalog — the baseline a System32
//! service-masquerade detector subtracts legitimate binaries against.
//!
//! A common adversary technique is to register a malicious standalone `.exe` as
//! a Windows service and drop it in `System32` under a plausible name, so it
//! blends in with the dozens of legitimate standalone-OwnProcess service
//! executables that genuinely live there (MITRE ATT&CK
//! [T1036.005 — Masquerading: Match Legitimate Name or Location] and
//! [T1543.003 — Create or Modify System Process: Windows Service]). The DC01
//! `coreupdater.exe` implant in the DFIRMadness "Szechuan Sauce" case is the
//! canonical example: a type-`0x10` (`SERVICE_WIN32_OWN_PROCESS`), auto-start
//! service whose `ImagePath` is `C:\Windows\System32\coreupdater.exe` —
//! structurally indistinguishable from `dns.exe` / `msdtc.exe` / `ismserv.exe`
//! until you have a known-good list to subtract.
//!
//! [`processes`](crate::processes)'s `WINDOWS_MASQUERADE_TARGETS` covers the
//! most-*impersonated* core process names (a deny-style indicator list); this
//! module is the complementary **allow-style** baseline of legitimate *service*
//! executables. Finding a System32-resident OwnProcess service whose basename
//! is NOT in [`KNOWN_WINDOWS_SERVICE_BINARIES`] is a **lead**, not a verdict —
//! it warrants signature / path / hash / ancestry corroboration.
//!
//! ## Scope
//!
//! [`KNOWN_WINDOWS_SERVICE_BINARIES`] entries are lowercase basenames of
//! legitimate **standalone OwnProcess** (`SERVICE_WIN32_OWN_PROCESS`, type
//! `0x10`) service executables that ship in `System32` / `SysWOW64`. The vast
//! majority of Windows services are `svchost.exe`-hosted
//! (`SERVICE_WIN32_SHARE_PROCESS`, type `0x20`) and carry a `ServiceDll` rather
//! than a distinct image; those DLLs are catalogued separately in
//! [`KNOWN_WINDOWS_SERVICE_DLLS`] / [`is_known_service_dll`] — the complement
//! that baselines the svchost implant vector. Kernel/filesystem driver services
//! (types `0x01`/`0x02`, `.sys` images) are out of scope for both.
//!
//! ## NON-EXHAUSTIVE
//!
//! Windows ships hundreds of services and the set varies by OS version, edition,
//! installed roles, and optional features; third-party software adds its own
//! OwnProcess services. This catalog cannot be complete, and it deliberately
//! gates a *lead*, never a verdict. Absence from the list means "investigate",
//! not "malicious"; presence means "a binary with this name is a documented
//! legitimate Windows service image", not "this particular file is benign"
//! (a masquerade reuses a legit *name*). Corroborate with the on-disk path,
//! a code-signature / hash check, and process ancestry before concluding.
//!
//! # Sources
//!
//! - Microsoft — "Security guidelines for system services in Windows Server"
//! (per-service catalog: service name, image, startup type):
//! <https://learn.microsoft.com/en-us/windows-server/security/windows-services/security-guidelines-for-disabling-system-services-in-windows-server>
//! - Microsoft — Windows service architecture / SCM (`OwnProcess` vs
//! `ShareProcess`, image-path semantics):
//! <https://learn.microsoft.com/en-us/windows/win32/services/service-programs>
//! - Russinovich, Solomon & Ionescu — *Windows Internals, 7th ed.*, Chapter 9
//! ("Management mechanisms — Services"): SCM, service types, svchost grouping.
//! - SANS FOR508 — "Advanced Incident Response, Threat Hunting & Digital
//! Forensics": known-good service-binary baseline methodology.
//! - Elastic Security — "Persistence via a Windows Service" / service-image
//! anomaly detection rules:
//! <https://www.elastic.co/guide/en/security/current/persistence-via-a-windows-service.html>
//! - MITRE ATT&CK T1036.005 / T1543.003:
//! <https://attack.mitre.org/techniques/T1036/005/> ·
//! <https://attack.mitre.org/techniques/T1543/003/>
//!
//! [T1036.005 — Masquerading: Match Legitimate Name or Location]: https://attack.mitre.org/techniques/T1036/005/
//! [T1543.003 — Create or Modify System Process: Windows Service]: https://attack.mitre.org/techniques/T1543/003/
/// The generic Windows service host binary. Most Windows services are NOT
/// standalone executables — they are DLLs (a `ServiceDll` under the service's
/// `Parameters` key) loaded into a shared `svchost.exe` process group
/// (`SERVICE_WIN32_SHARE_PROCESS`, type `0x20`). For those, the *image* is
/// always `svchost.exe`; the forensically interesting identifier is the
/// `ServiceDll`, baselined separately in [`KNOWN_WINDOWS_SERVICE_DLLS`].
///
/// Source: Windows Internals 7th ed., ch.9 (svchost service grouping);
/// <https://learn.microsoft.com/en-us/windows/win32/services/service-programs>.
pub const SVCHOST_HOST_BINARY: &str = "svchost.exe";
/// Lowercase basenames of legitimate **standalone OwnProcess** Windows service
/// executables that ship in `System32` / `SysWOW64`.
///
/// **NON-EXHAUSTIVE** — see the module docs. This gates a masquerade *lead*, not
/// a verdict. Each category is sourced in the comment above it.
pub const KNOWN_WINDOWS_SERVICE_BINARIES: & = &;
/// Returns `true` if `basename` is a known-good standalone Windows service
/// binary (case-insensitive; accepts the name with or without a `.exe` suffix).
///
/// This is an **allow-style lead gate**, not a verdict: a System32 OwnProcess
/// service whose image basename returns `false` warrants investigation, and a
/// `true` result only means the *name* is a documented legitimate service image
/// (a masquerade reuses a legit name — corroborate path / signature / hash).
/// See the module docs (NON-EXHAUSTIVE).
/// Lowercase `.dll` basenames of legitimate **svchost-hosted** Windows service
/// DLLs — the `ServiceDll` value under a service's `Parameters` key that a
/// `SERVICE_WIN32_SHARE_PROCESS` (type `0x20`) service loads into a shared
/// `svchost.exe` group.
///
/// This is the **complement** to [`KNOWN_WINDOWS_SERVICE_BINARIES`]: that list
/// baselines standalone OwnProcess service *exes*; this one baselines the *DLLs*
/// that svchost-hosted services load. Because `svchost.exe` is the same image
/// for every hosted service, the forensically interesting identifier is the
/// `ServiceDll`, and a *malicious* ServiceDll — a planted `.dll` registered as
/// the code a legitimate-looking service loads — is the **#1 svchost implant
/// vector** (MITRE ATT&CK
/// [T1543.003 — Create or Modify System Process: Windows Service] and
/// [T1036.005 — Masquerading: Match Legitimate Name or Location]). A
/// svchost-hosted service whose `ServiceDll` basename is NOT in this catalog,
/// or whose ServiceDll resolves outside `System32` (e.g. `\Temp\`, a user
/// profile, `ProgramData`), is a **lead**, not a verdict.
///
/// **NON-EXHAUSTIVE** — Windows ships hundreds of svchost-hosted services and
/// the set varies by OS version, edition, installed roles (a domain controller
/// loads AD-DS DLLs a workstation never has), and optional features; third-party
/// software registers its own ServiceDlls. This catalog cannot be complete and
/// it deliberately gates a *lead*, never a verdict. Absence means "investigate",
/// not "malicious"; presence means "a DLL with this name is a documented
/// legitimate Windows ServiceDll" — a masquerade reuses a legit *name*, so
/// corroborate with the on-disk path (must be `System32`), a code-signature /
/// hash check, and the hosting svchost group before concluding.
///
/// The bulk of this catalog (106 unique basenames) is the exact set of
/// `Parameters\ServiceDll` values observed on the genuine DFIRMadness "Szechuan
/// Sauce" DC01 `SYSTEM` hive (117 ServiceDll rows; several DLLs host multiple
/// services — `rpcss.dll` → `DcomLaunch`+`RpcSs`, `icsvc.dll` → 7 Hyper-V
/// integration services, `wdi.dll` → `WdiServiceHost`+`WdiSystemHost`). See
/// `tests/service_dlls_dc01_baseline.rs` for the baseline-completeness proof.
///
/// # Sources
///
/// - Microsoft — "Security guidelines for system services in Windows Server"
/// (per-service catalog, incl. svchost-hosted services and their DLLs):
/// <https://learn.microsoft.com/en-us/windows-server/security/windows-services/security-guidelines-for-disabling-system-services-in-windows-server>
/// - Russinovich, Solomon & Ionescu — *Windows Internals, 7th ed.*, Chapter 9
/// ("Management mechanisms — Services"): svchost grouping and `ServiceDll`.
/// - SANS FOR508 — "Advanced Incident Response, Threat Hunting & Digital
/// Forensics": svchost / ServiceDll known-good baseline methodology.
/// - Elastic Security — service-DLL anomaly detection rules (svchost loading a
/// ServiceDll from an unexpected path / unknown name):
/// <https://www.elastic.co/guide/en/security/current/persistence-via-a-windows-service.html>
/// - MITRE ATT&CK T1543.003 / T1036.005:
/// <https://attack.mitre.org/techniques/T1543/003/> ·
/// <https://attack.mitre.org/techniques/T1036/005/>
/// - Ground truth: DFIRMadness "Szechuan Sauce" DC01 `SYSTEM` hive (the genuine
/// 106-entry ServiceDll set), parsed via `winreg-core` in the validation test.
///
/// [T1543.003 — Create or Modify System Process: Windows Service]: https://attack.mitre.org/techniques/T1543/003/
/// [T1036.005 — Masquerading: Match Legitimate Name or Location]: https://attack.mitre.org/techniques/T1036/005/
pub const KNOWN_WINDOWS_SERVICE_DLLS: & = &;
/// Returns `true` if `basename` is a known-good svchost-hosted Windows
/// `ServiceDll` (case-insensitive; accepts the name with or without a `.dll`
/// suffix).
///
/// This is an **allow-style lead gate**, not a verdict: a svchost-hosted service
/// whose `ServiceDll` basename returns `false` — or whose ServiceDll resolves
/// outside `System32` — warrants investigation (T1543.003 / T1036.005), and a
/// `true` result only means the *name* is a documented legitimate ServiceDll
/// (a masquerade reuses a legit name — corroborate path / signature / hash).
/// See [`KNOWN_WINDOWS_SERVICE_DLLS`] (NON-EXHAUSTIVE).