GridinSoft Threat Intelligence

smss.exb file report

Clean record File reputation report
MD5 793c887d404f3ee2f9b490c21c38dd80
Latest seen 2021-01-12 20:41:01 (5 years ago)
First seen 2020-12-22 11:55:59 (5 years ago)
Size 152 KB
Publisher Microsoft Corporation
Product Microsoft® Windows® Operating System
Signed by Microsoft Windows Publisher

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-12-22 11:55:59 (5 years ago); latest analysis 2021-01-12 20:41:01 (5 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft® Windows® Operating System.

Digital signature

Signed by Microsoft Windows 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

smss.exb is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Windows® Operating System. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-12 20:41:01 (5 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: Microsoft® Windows® Operating System
Company Name: Microsoft Corporation
MD5: 793c887d404f3ee2f9b490c21c38dd80
Size: 152 KB
First Published: 2020-12-22 11:55:59 (5 years ago)
Latest Published: 2021-01-12 20:41:01 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-12 20:41:01 (5 years ago)

Overview

Signed By: Microsoft Windows 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:

%commonappdata%\net protector\nposfile\2020-12-09_0639
%commonappdata%\net protector\nposfile\2020-12-10_0633
%commonappdata%\net protector\nposfile\2020-12-22_0028
%commonappdata%\net protector\nposfile\2020-12-11_1200
%commonappdata%\net protector\nposfile\2020-12-02_1213
%commonappdata%\net protector\nposfile\2020-11-12_1101
%sysdrive%\zv\noexp
%commonappdata%\net protector\nposfile\2021-01-08_0548

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

Top country India
Share 100.0%
Low High activity

The strongest geographic signal for this file is India with 100.0% 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 100.0%

The most common operating system signal for smss.exb is Windows 10 with 100.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

smss.exb 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 0x000014f0
Image base 0x0000000140000000

PE Sections:

Sections 6
Raw data 144896

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

.text 86016 bytes · 59.4% of section data
MD5 fd403b2e9129f36cf5257afe53c4874d
.rdata 49664 bytes · 34.3% of section data
MD5 4d85f72431e00b5cfa70aa69d76405c3
.data 2048 bytes · 1.4% of section data
MD5 80da8b81682778183ec2a7c7af20d656
.pdata 4096 bytes · 2.8% of section data
MD5 bf67410ca33c5576c56c9571cada5150
.rsrc 2048 bytes · 1.4% of section data
MD5 31ff10fb3cabdbc92d41c1915bde5995
.reloc 1024 bytes · 0.7% of section data
MD5 be116dfd9eb359073fcd9cb622d1849a

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 793c887d404f3ee2f9b490c21c38dd80.
  • 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.