GridinSoft Threat Intelligence

Key.exe threat report

Detected as Trojan.Agent File reputation report
MD5 84c4432768e064f2ed2e7e6c9e2244a0
Latest seen 2023-05-18 23:10:04 (3 years ago)
First seen 2017-05-21 20:02:45 (9 years ago)
Size 18 KB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Agent. 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.Agent
Recommended action
Scan and remove
Last analysis
2023-05-18 23:10:04 (3 years ago)
File hash
84c4432768e064f2ed2e7e6c9e2244a0
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Agent.

Timeline

First seen 2017-05-21 20:02:45 (9 years ago); latest analysis 2023-05-18 23:10:04 (3 years ago).

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

Observed locations

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

  1. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

Key.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Trojan.Agent, based on the latest analysis from 2023-05-18 23:10:04 (3 years ago).

If Key.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.Agent.

MD5: 84c4432768e064f2ed2e7e6c9e2244a0
Size: 18 KB
First Published: 2017-05-21 20:02:45 (9 years ago)
Latest Published: 2023-05-18 23:10:04 (3 years ago)
Status: Trojan.Agent (on last analysis)
Analysis Date: 2023-05-18 23:10:04 (3 years ago)
Key.exe 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.

%profile%\downloads\compressed\[www.gigapurbalingga.com]_rvounp318\[www.gigapurbalingga.com]_rvounp318\patch.rar\patch
%profile%\downloads\compressed\revo uninstaller pro 3.1.8.kuyhaa.rar\revo uninstaller pro 3.1.8.kuyhaa\rup_3.1.0_registrator
%programfiles%\vs revo group\revo uninstaller pro
%profile%\google drive\backp 2017\backup_hd 2017\backp_ferreira\programas\revo uninstaller pro 3.1.4 final + crack [techtools.net]\revo uninstaller pro 3.1.4 final + crack [techtools.net]\revo uninstaller pro 3.1.4 final + crack [techtools.net]\rup_3.1.0_registrator.7z
%profile%\downloads\revo uninstaller pro 3.1.8 multilingual + fix
%profile%\downloads\revo.uninstaller.pro.3.1.8.softa\rup_3.1.0_registrator
%commonappdata%\vs revo group\revo uninstaller pro
%desktop%\programs\revo uninstaller pro version 3.1.8 (2017) incl patch-xenocoder and license code\patch-xenocoder
%profile%\downloads\revo uninstaller pro 3.1.9 + portable
%sysdrive%\downloads\revo uninstaller pro 3.1.9 + portable

ThreatInfo has observed Key.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.

RUP_3.1.0_Registrator.exe RUP_Registrator.exe Patch.exe Revo Uninstaller Pro 3.1.2 Crack.exe RUP_3.1.2_Registrator.exe RUP_3.1.x_Registrator.exe Patch Registrator Revo Uninstaller Pro.exe gRevo KeyGen_3.1.0_Registrator.exe Revo KeyGen_3.1.0_Registrator.exe Registrator.exe KG_ttrar.exe Registrator Revo Uninstaller Pro v3.1.5 Final.exe Active.exe RUP_3.1.1_Registrater.exe Ativador.exe vRUP_3.1.0_Registrator.exe RUP_3.x.0_Registrator.exe Key.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.

Windows 10 50.3%
Windows 7 39.4%
Windows 8.1 9.8%
Windows XP 0.6%

The most common operating system signal for Key.exe is Windows 10 with 50.3% 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.

Key.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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x00001adf
Image base 0x00400000

PE Sections:

Sections 3
Raw data 17850

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 8074 bytes · 45.2% of section data
MD5 3be45ee3f54e40c9c15968813441186a
.data 5620 bytes · 31.5% of section data
MD5 f4a076e3344a706113b51e643b32dbd5
.rsrc 4156 bytes · 23.3% of section data
MD5 513e24a3b21f26463e7b0b1584450b76

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.Agent

This report identifies Key.exe by MD5 84c4432768e064f2ed2e7e6c9e2244a0. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.

Download GridinSoft Anti-Malware Scan the device and confirm whether this exact hash is present. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 84c4432768e064f2ed2e7e6c9e2244a0.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan and remove the object if the same hash is found.