GridinSoft Threat Intelligence

SmartTagInstall.exe file report

Clean record File reputation report
MD5 00246cb936e5d25f6abb9b35dc643e2d
Latest seen 2021-07-07 20:53:12 (4 years ago)
First seen 2021-07-07 20:53:12 (4 years ago)
Size 29 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-07-07 20:53:12 (4 years ago); latest analysis 2021-07-07 20:53:12 (4 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft Office.

Digital signature

Signed by Microsoft Corporation. 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.

SmartTagInstall.exe is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft Office. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-07-07 20:53:12 (4 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: Microsoft Office
Company Name: Microsoft Corporation
MD5: 00246cb936e5d25f6abb9b35dc643e2d
Size: 29 KB
First Published: 2021-07-07 20:53:12 (4 years ago)
Latest Published: 2021-07-07 20:53:12 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-07-07 20:53:12 (4 years ago)
Signed By: Microsoft Corporation
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%\microsoft office\root\vfs\programfilescommonx86\microsoft shared

ThreatInfo has observed SmartTagInstall.exe 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 SmartTagInstall.exe 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.

SmartTagInstall.exe is identified as pe for 32-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows CUI
Entry point 0x00001285
Image base 0x00400000

PE Sections:

Sections 5
Raw data 11264

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

.text 5120 bytes · 45.5% of section data
MD5 7edf348d6523b302724687f50f1fa64e
.rdata 3072 bytes · 27.3% of section data
MD5 326bad50b04112e59bf8d1691bfa165e
.data 512 bytes · 4.5% of section data
MD5 48c19818ebd32aacce2a6e6af9595970
.rsrc 2048 bytes · 18.2% of section data
MD5 78fbd89fff4c9db9a5398c67bb975647
.reloc 512 bytes · 4.5% of section data
MD5 e4ba7f49cf0aacfc73cf1d8c101a2623

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 00246cb936e5d25f6abb9b35dc643e2d.
  • 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.