iCUE.exe threat report

MD5 8a3dd7bdf2e56cf191f7b72f41cf123e
Latest seen 2025-10-23 23:00:58 (7 months ago)
First seen 2025-10-23 23:00:58 (7 months ago)
Size 611 KB
Product iCUE

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Kryptik. 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.Kryptik
Recommended action
Scan and remove
Last analysis
2025-10-23 23:00:58 (7 months ago)
File hash
8a3dd7bdf2e56cf191f7b72f41cf123e
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Kryptik.

Timeline

First seen 2025-10-23 23:00:58 (7 months ago); latest analysis 2025-10-23 23:00:58 (7 months ago).

Publisher context

Company metadata: Corsair Memory, Inc.. Product metadata: iCUE.

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.

iCUE.exe is a Windows file recorded in the ThreatInfo database. It is associated with iCUE. The reported company name is Corsair Memory, Inc.. The current detection status is Trojan.Kryptik, based on the latest analysis from 2025-10-23 23:00:58 (7 months ago).

If iCUE.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.Kryptik.

Product Name: iCUE
Company Name: Corsair Memory, Inc.
MD5: 8a3dd7bdf2e56cf191f7b72f41cf123e
Size: 611 KB
First Published: 2025-10-23 23:00:58 (7 months ago)
Latest Published: 2025-10-23 23:00:58 (7 months ago)
Status: Trojan.Kryptik (on last analysis)
Analysis Date: 2025-10-23 23:00:58 (7 months ago)
iCUE.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.

%programfiles%\corsair

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

100.0%

The strongest geographic signal for this file is Colombia with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for iCUE.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.

iCUE.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: 0x0000000140000000
Entry Address: 0x0000231f

PE Sections:

Name Size of data MD5
.text 253952 c18cf3c72d27402e62ab398c3d697189
.rdata 220672 3d136ba79b46e69d7c6c3385512f8f16
.data 3584 c68c965279e7e1b6df578575805b47e0
.pdata 12800 22a696de5c5e2914a57fa900b265a8d0
.idata 13824 68a4ec80e3388186469f975027adf6b0
.tls 1024 c573bd7cea296a9c5d230ca6b5aee1a6
.00cfg 512 6ab8656b4a3f2e192127b3eede3707a3
.rsrc 116224 d9091bb805c62a763edf890d3502e5dc
.reloc 2560 55e67bf6ca75743154b48a34682a390b

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: