GridinSoft Threat Intelligence

libeay32.dll file report

Under review File reputation report
MD5 cdbdef73515997355e81a99421c1d721
Latest seen 2023-02-10 23:46:06 (3 years ago)
First seen 2017-05-22 11:21:48 (8 years ago)
Size 992 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 11:21:48 (8 years ago); latest analysis 2023-02-10 23:46:06 (3 years ago).

Publisher context

Company metadata: The OpenSSL Project, http://www.openssl.org/. Product metadata: The OpenSSL Toolkit.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

libeay32.dll is a Windows file recorded in the ThreatInfo database. It is associated with The OpenSSL Toolkit. The reported company name is The OpenSSL Project, http://www.openssl.org/. The current detection status is Undefined, based on the latest analysis from 2023-02-10 23:46:06 (3 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: The OpenSSL Toolkit
Company Name: The OpenSSL Project, http://www.openssl.org/
MD5: cdbdef73515997355e81a99421c1d721
Size: 992 KB
First Published: 2017-05-22 11:21:48 (8 years ago)
Latest Published: 2023-02-10 23:46:06 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-02-10 23:46:06 (3 years ago)
%programfiles%\etax2012
%programfiles%\etax2013
%programfiles%\4shared desktop
%programfiles%
%programfiles%\pity

ThreatInfo has observed libeay32.dll in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

Windows 7 46.2%
Windows 10 38.4%
Windows 8.1 9.0%
Windows Vista 2.9%
Windows 8 1.7%
Windows XP 1.7%

The most common operating system signal for libeay32.dll is Windows 7 with 46.2% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

libeay32.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows CUI
Entry point 0x000a13da
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1011712

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 659456 bytes · 65.2% of section data
MD5 df8e45a375f4d691827b544c8f516907
.rdata 249856 bytes · 24.7% of section data
MD5 1e0c8facafed2d0e2ba02e71b277821d
.data 57344 bytes · 5.7% of section data
MD5 969a1e4f782264d0a48fa544692a6c5f
.rsrc 4096 bytes · 0.4% of section data
MD5 95819de586126b626682ba0ff85d0714
.reloc 40960 bytes · 4.0% of section data
MD5 7ee0b888d30eba22c3bda7209688ba05

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

Report conclusion

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with cdbdef73515997355e81a99421c1d721.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.