GridinSoft Threat Intelligence
AdskAccessUIHost.exe file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2024-03-20 23:03:03 (2 years ago); latest analysis 2024-03-20 23:03:03 (2 years ago).
Company metadata: Autodesk, Inc.. Product metadata: Autodesk Access User Interface.
Signed by Autodesk, Inc.. ThreatInfo marks this publisher as trusted for this record.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
AdskAccessUIHost.exe is a Windows file recorded in the ThreatInfo database. It is associated with Autodesk Access User Interface. The reported company name is Autodesk, Inc.. The current detection status is Clean, based on the latest analysis from 2024-03-20 23:03:03 (2 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: | Autodesk Access User Interface |
| Company Name: | Autodesk, Inc. |
| MD5: | a50582d23071f4f080520a9afe611aab |
| Size: | 143 MB |
| First Published: | 2024-03-20 23:03:03 (2 years ago) |
| Latest Published: | 2024-03-20 23:03:03 (2 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2024-03-20 23:03:03 (2 years ago) |
Overview
| Signed By: | Autodesk, Inc. |
| 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%\autodesk\adodis\v1\setup |
ThreatInfo has observed AdskAccessUIHost.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.
Geographic signal
Observed country distribution
ThreatInfo has seen AdskAccessUIHost.exe across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Egypt 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:
The most common operating system signal for AdskAccessUIHost.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.
Analysis
AdskAccessUIHost.exe is identified as pe for 64-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
57dd19dbd27c03397629667c2622ab66
2623d2f887507d3d77827faf9bf3f0f1
e327f7602100ab91940a5f261877f6ca
4427e4167dae52e29a1546fbeb126ee1
8227fd15022110f8c3dc2bec1fe86fed
9d18e0a85b937c6d5925ee8189ffd9cb
d71c80853fa92a73d6e7b213fb3fe5de
ab87d2e8f7e7a40ee320b1ce20d19e20
613103b6e6f3d1dbefa183b6216f295f
7f78806522502dece0d90a1162a56d9f
60d3ea61d541c9be2e845d2787fb9574
9201087933ce6e1c6eda7b7d7eb86540
7e2c0ca5e75f6f66acceced0b8d5b1c4
2e64765a42294c49fc7d485874ff5594
3dc913c7ada19e0470d6c58b70c62c34
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.