GridinSoft Threat Intelligence

amselam.sys file report

Clean record File reputation report
MD5 2c89a100c30bcff13fe0e6aab0e77f44
Latest seen 2026-05-13 20:01:14 (2 weeks ago)
First seen 2019-09-02 17:46:34 (6 years ago)
Size 21 KB
Publisher Avira Operations GmbH & Co. KG
Product Anti-Malware SDK
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 2019-09-02 17:46:34 (6 years ago); latest analysis 2026-05-13 20:01:14 (2 weeks ago).

Publisher context

Company metadata: Avira Operations GmbH & Co. KG. Product metadata: Anti-Malware SDK.

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

amselam.sys is a Windows file recorded in the ThreatInfo database. It is associated with Anti-Malware SDK. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2026-05-13 20:01:14 (2 weeks 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: Anti-Malware SDK
Company Name: Avira Operations GmbH & Co. KG
MD5: 2c89a100c30bcff13fe0e6aab0e77f44
Size: 21 KB
First Published: 2019-09-02 17:46:34 (6 years ago)
Latest Published: 2026-05-13 20:01:14 (2 weeks ago)
Status: Clean (on last analysis)
Analysis Date: 2026-05-13 20:01:14 (2 weeks 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\savapi\elam_ppl\win64
%programfiles%\scanguard\savapi\elam_ppl\win64
%programfiles%\totalav\savapi
%programfiles%\pcprotect\savapi\elam_ppl\win64
%programfiles%\pcprotect\savapi
%programfiles%\scanguard\savapi
%commonappdata%\totalav\updates\savapi 6.0.0\elam_ppl\win64
%commonappdata%\totalav\updates\savapi 5.0.0\elam_ppl\win64
%commonappdata%\totalav\updates\savapi 8.0.0\elam_ppl\win64
%commonappdata%\totalav\updates\savapi 8.0.1\elam_ppl\win64

ThreatInfo has observed amselam.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 amselam.sys across 111 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 12.3%
Low High activity

The strongest geographic signal for this file is United States with 12.3% 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 85.3%
Windows 7 10.4%
Windows 8.1 3.3%
Windows 8 0.3%
Windows Server 2012 R2 0.3%
Windows Vista 0.2%
Windows Server 2016 0.1%
Windows Embedded Standard 0.1%
Windows Server 2012 0.1%
Windows Server 2008 R2 0.1%

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

amselam.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 0x00001830
Image base 0x0000000140000000

PE Sections:

Sections 8
Raw data 12288

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

.text 4608 bytes · 37.5% of section data
MD5 79378ed325d8570a218975642e8563b9
.rdata 2048 bytes · 16.7% of section data
MD5 9a0ddab2c4780f5dd8d058bd8e357496
.data 512 bytes · 4.2% of section data
MD5 790da9405e1321c1d4bf9a9c40e03f32
.pdata 512 bytes · 4.2% of section data
MD5 f11d1b7dd6d1f9e3e1a0279ea103c8d7
PAGE 1536 bytes · 12.5% of section data
Uncommon name
MD5 58fba49e5e0c336228c359edd21fdb7c
INIT 1024 bytes · 8.3% of section data
Uncommon name
MD5 7bf531d6ddb8d81501acbec99282e44f
.rsrc 1536 bytes · 12.5% of section data
MD5 5d302efd1287d8582551a34033af8e0a
.reloc 512 bytes · 4.2% of section data
MD5 be2a2422f9436d7b6d4199bb15534ef6

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 2c89a100c30bcff13fe0e6aab0e77f44.
  • 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.