GridinSoft Threat Intelligence

prefs_enclave_x64.dll file report

Under review File reputation report
MD5 b145d9fb04de6f3a5a01bb9f9f59d2ed
Latest seen 2024-10-07 23:01:37 (2 years ago)
First seen 2024-10-03 23:01:34 (2 years ago)
Size 113 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-10-03 23:01:34 (2 years ago); latest analysis 2024-10-07 23:01:37 (2 years ago).

Digital signature

Signed by Microsoft Corp Enclave Signer;Microsoft Corporation. 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.

prefs_enclave_x64.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2024-10-07 23:01:37 (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.

MD5: b145d9fb04de6f3a5a01bb9f9f59d2ed
Size: 113 KB
First Published: 2024-10-03 23:01:34 (2 years ago)
Latest Published: 2024-10-07 23:01:37 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-10-07 23:01:37 (2 years ago)

The signature on prefs_enclave_x64.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%\microsoft\edge\application
%programfiles%\microsoft\edgecore
%programfiles%\microsoft\edgewebview\application

ThreatInfo has observed prefs_enclave_x64.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 prefs_enclave_x64.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.

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

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x00001d00
Image base 0x0000000180000000

PE Sections:

Sections 5
Raw data 93696

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

.text 71168 bytes · 76.0% of section data
MD5 841ef6968a64279ddb0811cfff09e98f
.rdata 16896 bytes · 18.0% of section data
MD5 69e706272e3a4d7a927ab897c5014228
.data 1024 bytes · 1.1% of section data
MD5 5608b020c075660623399aa2d6a887fd
.pdata 4096 bytes · 4.4% of section data
MD5 fa52effa2b28ae6a15ba77e2796c49ef
.reloc 512 bytes · 0.5% of section data
MD5 a5a40288572486c3682a6146587b823c

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 b145d9fb04de6f3a5a01bb9f9f59d2ed.
  • 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.