Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Files in System32/SysWOW64 that aren't present in WinSxS analyzer #1509

Open
binglot opened this issue Dec 7, 2020 · 0 comments
Open

Files in System32/SysWOW64 that aren't present in WinSxS analyzer #1509

binglot opened this issue Dec 7, 2020 · 0 comments

Comments

@binglot
Copy link
Collaborator

binglot commented Dec 7, 2020

Allegedly, in modern Windows versions, most files in %windir%\System32 and %windir%\SysWOW64 have a corresponding file (a hard link?) in %windir%\WinSxS. As such, it'd be relatively easy to highlight which files in those directories aren't part of the OS. This would be useful when looking for a malware infection.

Create an analyzer that tags PE files (.EXE/.DLL/.SYS) in System32/SysWOW64 that don't occur in the WinSxS directory. Either by comparing the file system metadata (the "inode" is the same) or the file hash.

Example:

  • C:\Windows\SysWOW64\net.exe
    • inode: 121849
    • sha256_hash: d468e6b1b79555ac8bce0300942fd479689eb8f159f3a399848d3bf9b9990a56
  • C:\Windows\winsxs\x86_microsoft-windows-net-command-line-tool_31bf3856ad364e35_6.1.7600.16385_none_5208a7a3d3caa54c\net.exe
    • inode: 121849
    • sha256_hash: d468e6b1b79555ac8bce0300942fd479689eb8f159f3a399848d3bf9b9990a56
@jaegeral jaegeral added this to the Future milestone Jul 7, 2021
@berggren berggren removed this from the Future milestone Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants