GridinSoft Threat Intelligence

libeay32.dll file report

Under review File reputation report
MD5 88cb7054970146e4538079dcc55f8271
Latest seen 2026-02-19 23:00:58 (3 months ago)
First seen 2026-02-19 23:00:58 (3 months ago)
Size 1 MB
Publisher Outbyte
Product PC Repair

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2026-02-19 23:00:58 (3 months ago); latest analysis 2026-02-19 23:00:58 (3 months ago).

Publisher context

Company metadata: Outbyte . Product metadata: PC Repair .

Digital signature

Signed by Outbyte Computing Pty Ltd. The signature is reported as valid, but signed files can still be bundled or abused.

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 PC Repair . The reported company name is Outbyte . The current detection status is Undefined, based on the latest analysis from 2026-02-19 23:00:58 (3 months 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: PC Repair
Company Name: Outbyte
MD5: 88cb7054970146e4538079dcc55f8271
Size: 1 MB
First Published: 2026-02-19 23:00:58 (3 months ago)
Latest Published: 2026-02-19 23:00:58 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-19 23:00:58 (3 months ago)
Signed By: Outbyte Computing Pty Ltd
Status: Valid

The signature on libeay32.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%programfiles%\outbyte

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 100.0%

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

PE Sections:

Sections 5
Raw data 1379840

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

.text 952320 bytes · 69.0% of section data
MD5 ecf1daab44eb8cf8487a74758fe98733
.rdata 350720 bytes · 25.4% of section data
MD5 fad57a0b0bc97536acc61b9ba33824f5
.data 29696 bytes · 2.2% of section data
MD5 18d50f3f928fe0cd094cebd153f9461f
.rsrc 1536 bytes · 0.1% of section data
MD5 3d43c84699c9501174f611ff8b41b9ce
.reloc 45568 bytes · 3.3% of section data
MD5 cf330cd1889989c33a2278db70f9cce5

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 88cb7054970146e4538079dcc55f8271.
  • 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.