protected_elam.sys file report

MD5 9bee915715ccabb945154f4706f49325
Latest seen 2023-02-08 23:22:53 (3 years ago)
First seen 2021-11-15 21:52:56 (4 years ago)
Size 17 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-11-15 21:52:56 (4 years ago); latest analysis 2023-02-08 23:22:53 (3 years 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.

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.

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)
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.

%programfiles%\totalav\protected_elam
%programfiles%\totalav\protected_elam
%programfiles%\totalav\protected_elam
%programfiles%\totalav\protected_elam
%programfiles%\totalav\protected_elam
%programfiles%\totalav\protected_elam
%programfiles%\totalav\protected_elam
%programfiles%\totalav\protected_elam
%programfiles%\totalav\protected_elam
%programfiles%\totalav\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.

13.9%
11.1%
8.3%
8.3%
8.3%
8.3%
5.6%
5.6%
2.8%
2.8%
2.8%
2.8%
2.8%
2.8%
2.8%
2.8%
2.8%
2.8%
2.8%

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.

Windows 10 97.3%
Windows 7 2.7%

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.

protected_elam.sys is identified as pe for 64 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.

Subsystem: Native
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x000010b0

PE Sections:

Name Size of data MD5
.text 1536 e5b51a3f34fe347616196b962e579eb1
.rdata 2560 b54ab267e5b79d0b3896076c970dcc48
.data 512 ca87aeecac102438f7bc44455403eb2b
.pdata 512 b06f1051adb0d961992fdf278c0060eb
INIT 1024 1a9c982b29a94ec08305f442bdee73f6
.rsrc 1536 30a5aeb20309fff2dfb821bb02fea562
.reloc 512 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.

More information: