crysis2.exe threat report
ThreatInfo file report
crysis2.exe
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as Trojan.Obfuscator. 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.Obfuscator
- Recommended action
- Scan and remove
- Last analysis
- 2023-05-05 23:11:35 (3 years ago)
- File hash
- 7130ab5c5a0575c9bbd9627b566eae33
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Trojan.Obfuscator.
First seen 2018-08-04 18:11:33 (7 years ago); latest analysis 2023-05-05 23:11:35 (3 years ago).
Company metadata: Crytek GmbH. Product metadata: Crysis 2 (TM).
This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.
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
crysis2.exe is a Windows file recorded in the ThreatInfo database. It is associated with Crysis 2 (TM). The reported company name is Crytek GmbH. The current detection status is Trojan.Obfuscator, based on the latest analysis from 2023-05-05 23:11:35 (3 years ago).
If crysis2.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.Obfuscator.
File Details
| Product Name: | Crysis 2 (TM) |
| Company Name: | Crytek GmbH |
| MD5: | 7130ab5c5a0575c9bbd9627b566eae33 |
| Size: | 38 MB |
| First Published: | 2018-08-04 18:11:33 (7 years ago) |
| Latest Published: | 2023-05-05 23:11:35 (3 years ago) |
| Status: | Trojan.Obfuscator (on last analysis) | |
| Analysis Date: | 2023-05-05 23:11:35 (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:
| %sysdrive%\games\crysis 2 game of the year |
| %sysdrive%\geme\crysis 2 game of the year |
| %sysdrive%\geims\geyims\games\crysis 2 game of the year\crysis 2 game of the year |
| %sysdrive%\= games =\crysis 2 game of the year |
| %sysdrive%\victor\games\crysis 2 game of the year |
| %sysdrive%\crysis 2 game of the year |
| %sysdrive%\crysis 2 game of the year |
ThreatInfo has observed crysis2.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.
File Names:
| Crysis2.exe |
| crysis2.exe |
This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.
Geography:
| 87.5% | ||
| 12.5% |
The strongest geographic signal for this file is Russian Federation with 87.5% 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 | 50.0% | |
| Windows 7 | 25.0% | |
| Windows 8.1 | 25.0% |
The most common operating system signal for crysis2.exe is Windows 10 with 50.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
crysis2.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: | 0x01d86222 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 18129408 | 559bfdee9edb79bdf7f68d9b1e366d7d |
| PSFD00 | 7680 | c659dc540eb2623e1db415d9ebac2725 |
| .rdata | 1792000 | 6beee0270e04b816030fd0826ea1d9cb |
| .data | 131584 | 47a4ba15bf7c08fa10cbbd06c7f25cbe |
| .tls | 512 | bf619eac0cdf3f68d496ea9344137e8b |
| .rsrc | 377344 | 356b5ad6703de53a46a4b519bb55895e |
| PROTECT1 | 4096 | a6570725b8f8701afbcb6a0226596ddb |
| PROTECT2 | 0 | 00000000000000000000000000000000 |
| PROTECT3 | 17016832 | 4b0d170549e0c4a6f43b633bce33e506 |
| PROTECT4 | 3203072 | 85cde0512b535deaa89884c0a036ad70 |
| PROTECT5 | 18432 | 4d1927f6331844a07b04edecc103ab8e |
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:
