GridinSoft Threat Intelligence

styshwiz.exe file report

Clean record File reputation report
MD5 cabd2426ff114d0a4a29f7e4557865ea
Latest seen 2021-02-01 14:31:24 (5 years ago)
First seen 2021-02-01 14:29:34 (5 years ago)
Size 104 KB
Publisher Autodesk, Inc.
Signed by Autodesk, Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-02-01 14:29:34 (5 years ago); latest analysis 2021-02-01 14:31:24 (5 years ago).

Publisher context

Company metadata: Autodesk, Inc.. Product metadata: Autodesk Hardcopy Subsystem.

Digital signature

Signed by Autodesk, Inc. 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.

styshwiz.exe is a Windows file recorded in the ThreatInfo database. It is associated with Autodesk Hardcopy Subsystem. The reported company name is Autodesk, Inc.. The current detection status is Clean, based on the latest analysis from 2021-02-01 14:31:24 (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.

Product Name: Autodesk Hardcopy Subsystem
Company Name: Autodesk, Inc.
MD5: cabd2426ff114d0a4a29f7e4557865ea
Size: 104 KB
First Published: 2021-02-01 14:29:34 (5 years ago)
Latest Published: 2021-02-01 14:31:24 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-01 14:31:24 (5 years ago)
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.

%programfiles%

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

styshwiz.exe is identified as pe for 32-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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x00009870
Image base 0x00400000

PE Sections:

Sections 4
Raw data 100864

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

.text 40960 bytes · 40.6% of section data
MD5 f2b1bde7b37235a265dffa14fd3a257f
.rdata 22528 bytes · 22.3% of section data
MD5 24193f4008e827635ee5cea1632e5da1
.data 1024 bytes · 1.0% of section data
MD5 c407f5477b099536706d293d5ad7b522
.rsrc 36352 bytes · 36.0% of section data
MD5 e8db5cdadec777ff4a70cd9bfacd0639

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