GridinSoft Threat Intelligence

libeay32.dll file report

Under review File reputation report
MD5 148e4bc46ca9201e4b922bcf54dfbff7
Latest seen 2024-03-22 23:01:03 (2 years ago)
First seen 2017-05-26 14:07:45 (8 years ago)
Size 1 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-26 14:07:45 (8 years ago); latest analysis 2024-03-22 23:01:03 (2 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 2024-03-22 23:01:03 (2 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: 148e4bc46ca9201e4b922bcf54dfbff7
Size: 1 MB
First Published: 2017-05-26 14:07:45 (8 years ago)
Latest Published: 2024-03-22 23:01:03 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-03-22 23:01:03 (2 years ago)
%programfiles%\baofeng\stormplayer\core\codecs
%programfiles%\baofeng\magicencoder\core\codecs
%programfiles%\baofeng\stormplayer\core
%programfiles%\baofeng\magicencoder\core
%programfiles%\baofeng\webplayerlite\core

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 10 69.5%
Windows 7 18.8%
Windows 8.1 5.5%
Windows XP 3.9%
Windows Server 2003 0.8%
Windows Server 2008 R2 0.8%
Windows 8 0.8%

The most common operating system signal for libeay32.dll is Windows 10 with 69.5% 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 0x000ae22f
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1105920

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

.text 710656 bytes · 64.3% of section data
MD5 cb893f5f2c1173c526a175a642ef35d7
.rdata 333824 bytes · 30.2% of section data
MD5 2828a213d1f72256c46ea353fa6ae3ea
.data 19456 bytes · 1.8% of section data
MD5 37a847167f9eb6c5d9abaa36c5ad9e2b
.rsrc 1536 bytes · 0.1% of section data
MD5 de2de761ea41d0deecf7da8964e96dda
.reloc 40448 bytes · 3.7% of section data
MD5 8f9211eba3ff778cac216f4fbacf8c67

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 148e4bc46ca9201e4b922bcf54dfbff7.
  • 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.