GridinSoft Threat Intelligence

smss.exb file report

Clean record File reputation report
MD5 c2c989b9ec32183a7baf5c0d59a57042
Latest seen 2021-05-11 21:00:31 (5 years ago)
First seen 2018-07-13 18:15:19 (7 years ago)
Size 140 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-07-13 18:15:19 (7 years ago); latest analysis 2021-05-11 21:00:31 (5 years ago).

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.

smss.exb is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2021-05-11 21:00:31 (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.

MD5: c2c989b9ec32183a7baf5c0d59a57042
Size: 140 KB
First Published: 2018-07-13 18:15:19 (7 years ago)
Latest Published: 2021-05-11 21:00:31 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-05-11 21:00:31 (5 years ago)
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.

%commonappdata%\net protector\nposfile\2018-07-13_2200
%commonappdata%\net protector\nposfile\2020-10-01_0959
%commonappdata%\net protector\nposfile\2021-05-05_1114

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.

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.

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 0x000011a0
Image base 0x0000000140000000

PE Sections:

Sections 6
Raw data 133120

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

.text 76288 bytes · 57.3% of section data
MD5 0795ddae5cd67a89e557e375831b0adb
.rdata 47616 bytes · 35.8% of section data
MD5 7db23a9203077a7405c46bf5d9dff5bb
.data 2048 bytes · 1.5% of section data
MD5 ef92c120b50a19dcc173af6af2a15f7b
.pdata 4096 bytes · 3.1% of section data
MD5 06b0c1c23db348de537203fe6a8a94e5
.rsrc 2048 bytes · 1.5% of section data
MD5 a1de043ddad5abedfe4ebf0989e5250e
.reloc 1024 bytes · 0.8% of section data
MD5 ed75f22f20801c91babf5c2f50c36b38

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