fveapi.dll
Windows BitLocker Drive Encryption API file version info
Library on Windows 2 known copies with hashes 1 Sigma rule names it
Is it the real fveapi.dll?
Installed in
C:\Windows\system32\C:\Windows\SysWOW64\Signed byMicrosoft Windows
ProductMicrosoft Windows Operating System, Microsoft Corporation
DescriptionWindows BitLocker Drive Encryption API
2 known copies
10.0.19041.488 (WinBuild.160101.0800) · C:\Windows\SysWOW64\fveapi.dll · signed by Microsoft Windows
39f26ff9bf04d9f4b56fde0ce1a9294b6925571cf38e37be5a6490f258c2d68f10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\fveapi.dll · signed by Microsoft Windows
7f4556840dffc92a2fd38edf0033b2f51b09cd894871281d025c6a2c05ba66b9From 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 fveapi.dll in 1 rule, for every kind of event; none is a process creation rule CmdID evaluates, so none is listed.