GridinSoft Threat Intelligence

prefs_enclave_x64.dll file report

Under review File reputation report
MD5 0ad48ae9a232dba3be9d7a0ad188f9df
Latest seen 2024-10-31 23:01:40 (2 years ago)
First seen 2024-09-05 23:00:32 (2 years ago)
Size 119 KB
Signed by Microsoft Corp Enclave Signer;Microsoft Corporation

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-09-05 23:00:32 (2 years ago); latest analysis 2024-10-31 23:01:40 (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.

File context

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-31 23:01:40 (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.

File Details

MD5: 0ad48ae9a232dba3be9d7a0ad188f9df
Size: 119 KB
First Published: 2024-09-05 23:00:32 (2 years ago)
Latest Published: 2024-10-31 23:01:40 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-10-31 23:01:40 (2 years ago)

Overview

Signed By: Microsoft Corp Enclave Signer;Microsoft Corporation
Status: Valid

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.

Common Places:

%programfiles%\microsoft\edgecore
%programfiles%\microsoft\edgewebview\application
%programfiles%\microsoft\edge\application
%sysdrive%\$recycle.bin\s-1-5-21-4114190863-4098575981-4148236708-1001\$r2zmcow
%sysdrive%\$recycle.bin\s-1-5-21-4114190863-4098575981-4148236708-1001\$r6e103y
%windir%\winsxs
%system%
%commonappdata%\dell\saremediation\systemrepair\snapshots
%sysdrive%\windows.old\windows\winsxs
%sysdrive%\windows.old\windows\system32

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.

Geographic signal

Observed country distribution

ThreatInfo has seen prefs_enclave_x64.dll across 45 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 36.2%
Low High activity

The strongest geographic signal for this file is United States with 36.2% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 98.0%
Windows 8 2.0%

The most common operating system signal for prefs_enclave_x64.dll is Windows 10 with 98.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.

Analysis

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 0x00002d40
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 99328

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

.text 75264 bytes · 75.8% of section data
MD5 43b6bcf7f5c99235c9bb7ef772b98529
.rdata 16896 bytes · 17.0% of section data
MD5 39572ef3642ccc3eec65c357374d1dbd
.data 1024 bytes · 1.0% of section data
MD5 3f61add671d8affffc365f927d0df38c
.pdata 4096 bytes · 4.1% of section data
MD5 9437fb166359246bf6c76856c430dd71
memcpy_ 512 bytes · 0.5% of section data
Uncommon name
MD5 83df65dd0ba1fe31c5104efda0b1c453
_RDATA 1024 bytes · 1.0% of section data
Uncommon name
MD5 2f4c4ee4deac1159a406949acd8c4771
.reloc 512 bytes · 0.5% of section data
MD5 1abcc67da3b2f45206d0886fd42c4528

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 0ad48ae9a232dba3be9d7a0ad188f9df.
  • 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.