GridinSoft Threat Intelligence
protected_elam.sys file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2021-11-15 21:52:56 (4 years ago); latest analysis 2023-02-08 23:22:53 (3 years ago).
Company metadata: TODO: <Company name>. Product metadata: TODO: <Product name>.
Signed by Microsoft Windows Early Launch Anti-malware Publisher. ThreatInfo marks this publisher as trusted for this record.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
protected_elam.sys is a Windows file recorded in the ThreatInfo database. It is associated with TODO: <Product name>. The reported company name is TODO: <Company name>. The current detection status is Clean, based on the latest analysis from 2023-02-08 23:22:53 (3 years ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | TODO: <Product name> |
| Company Name: | TODO: <Company name> |
| MD5: | 9bee915715ccabb945154f4706f49325 |
| Size: | 17 KB |
| First Published: | 2021-11-15 21:52:56 (4 years ago) |
| Latest Published: | 2023-02-08 23:22:53 (3 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2023-02-08 23:22:53 (3 years ago) |
Overview
| Signed By: | Microsoft Windows Early Launch Anti-malware Publisher |
| Status: | Trusted Publisher |
ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.
Common Places:
| %programfiles%\totalav\protected_elam |
| %programfiles%\pcprotect\protected_elam |
| %programfiles%\scanguard\protected_elam |
| %commonappdata%\totalav\updates\5_17_470\extracted\protected_elam |
ThreatInfo has observed protected_elam.sys 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 protected_elam.sys across 19 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 13.9% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for protected_elam.sys is Windows 10 with 97.3% 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
protected_elam.sys is identified as pe for 64-bit systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
e5b51a3f34fe347616196b962e579eb1
b54ab267e5b79d0b3896076c970dcc48
ca87aeecac102438f7bc44455403eb2b
b06f1051adb0d961992fdf278c0060eb
1a9c982b29a94ec08305f442bdee73f6
30a5aeb20309fff2dfb821bb02fea562
f608df8564f9ce5f0993a1abaeeba7ca
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 hash is currently recorded as clean
Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.