api-ms-win-core-heap-l1-1-0.dll
ApiSet Stub DLL file version info
Library on Windows 7 known copies with hashes
Is it the real api-ms-win-core-heap-l1-1-0.dll?
apisetstub in the file’s header: a renamed copy still carries itC:\Program Files (x86)\Cisco Systems\Cisco Jabber\C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\arm\C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\x64\7 known copies
10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\arm\api-ms-win-core-heap-l1-1-0.dll · signed by Microsoft Windows Kits Publisher
2f52c5e620807d0a4e938000e2956473af77fd5bfdc90478cdc382fc853c91f910.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\x64\api-ms-win-core-heap-l1-1-0.dll · signed by Microsoft Windows
3bbbe0fdf572eb5bf3a800d625faa1fe0d864b126c95425d529870f719df731510.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Redist\10.0.19041.0\ucrt\DLLs\x86\api-ms-win-core-heap-l1-1-0.dll · signed by Microsoft Windows
4fce17577c2eab622835267bb5e355442221de85a0e481b4eef284a2eb0fdb0410.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\downlevel\api-ms-win-core-heap-l1-1-0.dll · signed by Microsoft Windows
61dfae09b998b4fb208c282a9c61523b810e8afdab6ef1abe6931aa2606bdb9c10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\api-ms-win-core-heap-l1-1-0.dll · signed by Microsoft Windows
c8adf90a32936eaf678ed9a091d422e091e6b80d0431ec120e60febe1f617ac310.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\downlevel\api-ms-win-core-heap-l1-1-0.dll · signed by Microsoft Windows
f77f70e79bdb238164fb25ad644798bd6526ad1aae82addaad4095a4b25bcb0d10.0.14393.33 (rs1_release_sec.160727-1952) · C:\Program Files (x86)\Cisco Systems\Cisco Jabber\api-ms-win-core-heap-l1-1-0.dll · signed by Microsoft Corporation
9a5952c82cbcb1a8ece9c51c258667d9ab96d13ec6455873999ff0bf78c3cab0From 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.