GridinSoft Threat Intelligence
clr.exe threat report
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
- 2021-11-18 21:23:52 (4 years ago)
- File hash
- f4ce0217b9c6fa0d5ef337c165634c99
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Trojan.Heur!.
First seen 2021-11-18 21:23:52 (4 years ago); latest analysis 2021-11-18 21:23:52 (4 years ago).
Company metadata: HP. Product metadata: ProcKeyHook.Properties.
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
- Compare the MD5 above with the file found on the device.
- Check whether the file appears in the observed locations or under one of the alternate names.
- Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.
File context
clr.exe is a Windows file recorded in the ThreatInfo database. It is associated with ProcKeyHook.Properties. The reported company name is HP. The current detection status is Trojan.Heur!, based on the latest analysis from 2021-11-18 21:23:52 (4 years ago).
If clr.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!.
File Details
| Product Name: | ProcKeyHook.Properties |
| Company Name: | HP |
| MD5: | f4ce0217b9c6fa0d5ef337c165634c99 |
| Size: | 3 MB |
| First Published: | 2021-11-18 21:23:52 (4 years ago) |
| Latest Published: | 2021-11-18 21:23:52 (4 years ago) |
| Status: | Trojan.Heur! (on last analysis) | |
| Analysis Date: | 2021-11-18 21:23:52 (4 years ago) |
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.
Common Places:
| %temp% |
ThreatInfo has observed clr.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.
Geography:
1 observed countriesThe strongest geographic signal for this file is Brazil 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 clr.exe is Windows 8.1 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
clr.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
c87dfa60c00eb68df7e3b146a37992c2
baf6a5ae4345932de150b8c51563ff93
8ef1fb8a95a6b3dd7459b8674e1b7b3f
af9bf975fe2719bc5ee6326783ee008b
bbba5177887e6addbeb16ebcea4a88cd
d41d8cd98f00b204e9800998ecf8427e
fac1d9e256899e5e0c10ba10884ec5c3
e6f4fda8e4f0e9542b0ea4e6e677aa7b
a990f5c202d447a937680abdc8702db7
d27d2fbbd3eae73b44d237af727133a1
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
GridinSoft detects this file as Trojan.Heur!
This report identifies clr.exe by MD5 f4ce0217b9c6fa0d5ef337c165634c99. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.