ssleay32.dll
OpenSSL Shared Library file version info
Library on Windows 3 known copies with hashes
Is it the real ssleay32.dll?
Installed in
C:\Program Files (x86)\Cisco Systems\Cisco Jabber\C:\Program Files (x86)\Microsoft Office\root\Office16\ODBC Drivers\Redshift\lib\OpenSSL32.DllA\C:\Program Files (x86)\Sennheiser\SenncomSDK\Signed byCisco Systems Inc.
ProductThe OpenSSL Toolkit, The OpenSSL Project, http://www.openssl.org/
DescriptionOpenSSL Shared Library
3 known copies
1.0.2u · C:\Program Files (x86)\Sennheiser\SenncomSDK\ssleay32.dll · not signed
0e21065e0bae0b1b71fb2a9f96c874f204507a9a28083789546ac6643df0bc221.0.2t.6.2.364 · C:\Program Files (x86)\Cisco Systems\Cisco Jabber\ssleay32.dll · signed by Cisco Systems Inc.
ac96384c0244d7662987c834e62bde4096beefaa9c4b12126d02ed6dd66da22c1.0.2j · C:\Program Files (x86)\Microsoft Office\root\Office16\ODBC Drivers\Redshift\lib\OpenSSL32.DllA\ssleay32.dll · not signed
bdb8774187c4260b987445b9a5ecd649d5cc56b08132bd144e63e0bfeeced949From 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.