GridinSoft Threat Intelligence

protected_elam.sys file report

Clean record File reputation report
MD5 e9806e894443f95671064755f9663a18
Latest seen 2026-04-28 23:01:37 (a month ago)
First seen 2022-10-22 23:24:36 (3 years ago)
Size 18 KB
Publisher TODO: <Company name>
Product TODO: <Product name>
Signed by Microsoft Windows Early Launch Anti-malware Publisher

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-10-22 23:24:36 (3 years ago); latest analysis 2026-04-28 23:01:37 (a month ago).

Publisher context

Company metadata: TODO: <Company name>. Product metadata: TODO: <Product name>.

Digital signature

Signed by Microsoft Windows Early Launch Anti-malware Publisher. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. 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 2026-04-28 23:01:37 (a month 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: e9806e894443f95671064755f9663a18
Size: 18 KB
First Published: 2022-10-22 23:24:36 (3 years ago)
Latest Published: 2026-04-28 23:01:37 (a month ago)
Status: Clean (on last analysis)
Analysis Date: 2026-04-28 23:01:37 (a month 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%\scanguard\protected_elam
%programfiles%\pcprotect\protected_elam
%commonappdata%\totalav\updates\6_2_121\prev\protected_elam
%commonappdata%\totalav\updates\6_2_121\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 36 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 33.9%
Low High activity

The strongest geographic signal for this file is United States with 33.9% 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 95.5%
Windows 7 2.7%
Windows Embedded 8.1 0.9%
Windows 8.1 0.9%

The most common operating system signal for protected_elam.sys is Windows 10 with 95.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.

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.

Format pe
Architecture 64-bit
Subsystem Native
Entry point 0x000010b0
Image base 0x0000000140000000

PE Sections:

Sections 7
Raw data 8192

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

.text 1536 bytes · 18.8% of section data
MD5 e5b51a3f34fe347616196b962e579eb1
.rdata 2560 bytes · 31.3% of section data
MD5 a6e22b7799f84f5955121a05953d9fd1
.data 512 bytes · 6.3% of section data
MD5 ca87aeecac102438f7bc44455403eb2b
.pdata 512 bytes · 6.3% of section data
MD5 b06f1051adb0d961992fdf278c0060eb
INIT 1024 bytes · 12.5% of section data
Uncommon name
MD5 1a9c982b29a94ec08305f442bdee73f6
.rsrc 1536 bytes · 18.8% of section data
MD5 96c3ad52efc691dd920e7ae041e82056
.reloc 512 bytes · 6.3% of section data
MD5 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.

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