creosysmon.exe threat report

MD5 a07cb8a255c53a67ba689706481bbc1f
Latest seen 2022-04-26 23:19:25 (4 years ago)
First seen 2022-04-26 23:19:25 (4 years ago)
Size 5 MB
Publisher PTC Inc.

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2022-04-26 23:19:25 (4 years ago)
File hash
a07cb8a255c53a67ba689706481bbc1f
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2022-04-26 23:19:25 (4 years ago); latest analysis 2022-04-26 23:19:25 (4 years ago).

Publisher context

Company metadata: PTC Inc.. Product metadata: Creo System Monitor.

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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

creosysmon.exe is a Windows file recorded in the ThreatInfo database. It is associated with Creo System Monitor. The reported company name is PTC Inc.. The current detection status is Trojan.Heur!, based on the latest analysis from 2022-04-26 23:19:25 (4 years ago).

If creosysmon.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Heur!.

Product Name: Creo System Monitor
Company Name: PTC Inc.
MD5: a07cb8a255c53a67ba689706481bbc1f
Size: 5 MB
First Published: 2022-04-26 23:19:25 (4 years ago)
Latest Published: 2022-04-26 23:19:25 (4 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2022-04-26 23:19:25 (4 years ago)
creosysmon.exe detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

%programfiles%\ptc\creo 6.0.0.0\common files\x86e_win64

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

100.0%

The strongest geographic signal for this file is Taiwan with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for creosysmon.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.

creosysmon.exe is identified as pe for 64 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x0032a51c

PE Sections:

Name Size of data MD5
.text 3331584 5b70b9c636bccec6f3f6aeb495106934
.rdata 744448 51440767461bf02b25b51d664de5d67f
.data 991744 e9e1fbb73f81a97a41e9cbdd5837afd8
.pdata 177152 0d0139f31d3b17bd07a31706eadc2e68
.datapro 512 c10d46de78cf5e80d5ba3459850e34f5
_RDATA 3072 e1d0b2eb3566bdaf034c800b9543fac8
.rsrc 8192 75005f680e7674d605a88627bb9c1be4
.reloc 23040 6f96e4bc41c83924cfc959ff659d3c9e

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.

More information: