tk64.exe threat report
ThreatInfo file report
tk64.exe
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as Possible Threat. 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
- Possible Threat
- Recommended action
- Scan and remove
- Last analysis
- 2025-07-20 23:01:59 (10 months ago)
- File hash
- dc3847c465e40daa6d619c34cad22f80
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Possible Threat.
First seen 2025-07-20 23:01:59 (10 months ago); latest analysis 2025-07-20 23:01:59 (10 months ago).
Company metadata: Gridinsoft LLC. Product metadata: Gridinsoft Trojan Killer Portable.
Signed by Gridinsoft TOV. 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
- 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
tk64.exe is a Windows file recorded in the ThreatInfo database. It is associated with Gridinsoft Trojan Killer Portable. The reported company name is Gridinsoft LLC. The current detection status is Possible Threat, based on the latest analysis from 2025-07-20 23:01:59 (10 months ago).
If tk64.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 Possible Threat.
File Details
| Product Name: | Gridinsoft Trojan Killer Portable |
| Company Name: | Gridinsoft LLC |
| MD5: | dc3847c465e40daa6d619c34cad22f80 |
| Size: | 20 MB |
| First Published: | 2025-07-20 23:01:59 (10 months ago) |
| Latest Published: | 2025-07-20 23:01:59 (10 months ago) |
| Status: | Possible Threat (on last analysis) | |
| Analysis Date: | 2025-07-20 23:01:59 (10 months 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.
Overview
| Signed By: | Gridinsoft TOV |
| Status: | Valid |
The signature on tk64.exe 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:
| %desktop%\desktop\aplicativos\instaladores\antivirus |
ThreatInfo has observed tk64.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 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:
| Windows 10 | 100.0% |
The most common operating system signal for tk64.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
tk64.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: | 0x0000000000400000 |
| Entry Address: | 0x00bca630 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 12547072 | 51f97a00c77c4ba568950f4ce7c92be4 |
| .data | 1149440 | 6f25402691746576e1b12cc0702028e2 |
| .bss | 0 | d41d8cd98f00b204e9800998ecf8427e |
| .idata | 35328 | ba8dc37076ffb089c18ef8f017df4546 |
| .didata | 5632 | cc817809ed662b8912b733c7078cd17e |
| .edata | 512 | 47dcbf8aa2013d284a0fab3a0df8e7f9 |
| .tls | 0 | d41d8cd98f00b204e9800998ecf8427e |
| .rdata | 512 | 413aa50370a092f84813ccf57f2a4665 |
| .reloc | 610304 | ed3216c252bd2121b8ef7b3991166efc |
| .pdata | 641024 | a14a64ab94f6ddfa5c30005743813e9a |
| .rsrc | 6492160 | 31837898938c43df5c8699a3ea243e41 |
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: