w32tm.exe
Windows Time Service Diagnostic Tool file version info
Program on Windows 14 known copies with hashes 3 Sigma rules name it Command w32tm
Is it the real w32tm.exe?
w32time.dll in the file’s header: a renamed copy still carries itC:\Windows\system32\C:\Windows\SysWOW64\14 known copies
10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\w32tm.exe · signed by Microsoft Windows
3961d423ca02fae486d3cbdcbda083bf6d851f93c5415b91a2653cc0f8c0aacd10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\w32tm.exe · signed by Microsoft Windows
8ed11d917168922e779fbb1062d757e8641d4251cd94cd52c474ae17ac6e1c1710.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\w32tm.exe · signed by Microsoft Windows
88f14176c848adce732fe1db67c2d95cd495ac71caed5d137e0108332509042f10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\w32tm.exe · signed by Microsoft Windows
8ab5c40895d73907b4f96ba73e73c5bf12a76a00965034a4146f85533b14f5c410.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\w32tm.exe · signed by Microsoft Windows
61009645625a99e7c2b2dcef4f77f7ff3c8894d43d4d9a856082e14c1a52780f10.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\w32tm.exe · signed by Microsoft Windows
67fb8c44c4e05b9b090bf839b1abfd389de633f4a987141bd705e173927eb48f10.0.17763.719 (WinBuild.160101.0800) · C:\Windows\SysWOW64\w32tm.exe · signed by Microsoft Windows
b98bde1672d51b66cdaef87936826773cb8637e34b5f63b9f1e10b0481ce3da810.0.17763.1490 (WinBuild.160101.0800) · C:\Windows\SysWOW64\w32tm.exe · signed by Microsoft Windows
52537a069c700f82683549dba51bc73b66130385d726497c1728dc5a0b80987d10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\w32tm.exe · signed by Microsoft Windows
a6068fdd06a779798be73420ae7e91544c23b96eb01d75a1be86ead8c0413e6b10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\w32tm.exe · signed by Microsoft Windows
c71b4316bf6ebd40a227e0fa3af899a00375c41d5029f55eb5880d6fb0a6a5f510.0.14393.0 (rs1_release.160715-1616) · C:\Windows\system32\w32tm.exe · signed by Microsoft Windows
6b71a1db48da5f0359ea3fbbd3dec449b7f91b00687617d0d6e979b5f0ab245910.0.14393.0 (rs1_release.160715-1616) · C:\Windows\SysWOW64\w32tm.exe · signed by Microsoft Windows
c879ce7de155ada43e5bfc5bacecd54529c8019b90f8be09ffa116a118be92d56.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\SysWOW64\w32tm.exe · not signed
15e9ef8fe24a1ce0ad23911b6ea10d3e56c8586ad310da7b994958f64eac92c16.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\system32\w32tm.exe · not signed
21fff3acf14af70e22d23028dc26bee58c8394707c61618ae1d35866dc9c4d51From the file’s version info and the copies recorded by xCyclopedia (MIT). A copy in another folder, signed by someone else or with another hash is not necessarily malicious, but it is worth a closer look. In Ceplin, "<sha256>".whatis() says which known copy a hash is.
What detects it
Sigma names w32tm.exe in 3 rules in all, for every kind of event; these are the process creation rules CmdID evaluates.