Why it matters
Evidence available for this file
No final classification is available yet.
Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.
First seen 2025-01-09 23:00:49 (a year ago); latest analysis 2025-01-09 23:00:49 (a year ago).
Company metadata: . Product metadata: ЕngineGame .
Signed by EngineGame. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
CheatEngine75(1).tmp is a Windows file recorded in the ThreatInfo database. It is associated with ЕngineGame . The reported company name is . The current detection status is Undefined, based on the latest analysis from 2025-01-09 23:00:49 (a year ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.
ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.
File Details
| Product Name: | ЕngineGame |
| Company Name: | |
| MD5: | 3f26413839bdf17ca613d5e8aa97af3e |
| Size: | 2 MB |
| First Published: | 2025-01-09 23:00:49 (a year ago) |
| Latest Published: | 2025-01-09 23:00:49 (a year ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2025-01-09 23:00:49 (a year ago) |
Overview
| Signed By: | EngineGame |
| Status: | Valid |
The signature on CheatEngine75(1).tmp is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.
Common Places:
| %temp% |
ThreatInfo has observed CheatEngine75(1).tmp 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.
Geographic signal
Observed country distribution
ThreatInfo has seen CheatEngine75(1).tmp across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Spain 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 CheatEngine75(1).tmp 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
CheatEngine75(1).tmp 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.
3498f77be9727e1ac8cc402bbc49ea0d
0d664c40cff0fa85e0fad028b8fa6a46
50c28bdf7afb4cf66d0de8f2bbf87963
d41d8cd98f00b204e9800998ecf8427e
c255c35dc8b2afb5a1e8a0d53ec7a7b6
79edfcd6f8ae7d102d66221793c2a056
54166a993ddfc95afd7da99ac7579d19
d41d8cd98f00b204e9800998ecf8427e
2bd0b4250f44ecdcc366775e042632aa
d4ca194198e80826cd4e031fa3d4f93b
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 file is still under review
ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.