XGz1X2bF.exe threat report
ThreatInfo file report
XGz1X2bF.exe
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as Suspicious Object. 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
- Suspicious Object
- Recommended action
- Scan and remove
- Last analysis
- 2023-03-05 23:17:17 (3 years ago)
- File hash
- adde70298d78be284a93b397cdcad11e
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Suspicious Object.
First seen 2023-03-05 23:17:17 (3 years ago); latest analysis 2023-03-05 23:17:17 (3 years ago).
Company metadata: iTop Inc.. Product metadata: Product Statistics.
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
XGz1X2bF.exe is a Windows file recorded in the ThreatInfo database. It is associated with Product Statistics. The reported company name is iTop Inc.. The current detection status is Suspicious Object, based on the latest analysis from 2023-03-05 23:17:17 (3 years ago).
If XGz1X2bF.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 Suspicious Object.
File Details
| Product Name: | Product Statistics |
| Company Name: | iTop Inc. |
| MD5: | adde70298d78be284a93b397cdcad11e |
| Size: | 727 MB |
| First Published: | 2023-03-05 23:17:17 (3 years ago) |
| Latest Published: | 2023-03-05 23:17:17 (3 years ago) |
| Status: | Suspicious Object (on last analysis) | |
| Analysis Date: | 2023-03-05 23:17:17 (3 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:
| %appdata% |
ThreatInfo has observed XGz1X2bF.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:
| 100.0% |
The strongest geographic signal for this file is Peru 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:
| Windows 10 | 100.0% |
The most common operating system signal for XGz1X2bF.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
XGz1X2bF.exe is identified as pe for 32 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: | 32 |
| Image Base: | 0x00400000 |
| Entry Address: | 0x00b377ee |
PE Sections:
| Name | Size of data | MD5 |
| .text | 0 | d41d8cd98f00b204e9800998ecf8427e |
| .rdata | 0 | d41d8cd98f00b204e9800998ecf8427e |
| .data | 0 | d41d8cd98f00b204e9800998ecf8427e |
| ./!| | 0 | d41d8cd98f00b204e9800998ecf8427e |
| .6cH | 1536 | b15609b5cbfb3b8c052178fc2abee60c |
| .nR0 | 7399936 | c37863d857cd09fa8149496067d24154 |
| .reloc | 1536 | 5be9141ce071d208b6a470c8698b296d |
| .rsrc | 114688 | a0b7eab9620576f806a04727dc945236 |
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: