IntelSvc.exe threat report

MD5 a7cde18f991e97037a7899b7669e2548
Latest seen 2025-10-15 23:00:28 (7 months ago)
First seen 2022-05-13 23:25:58 (3 years ago)
Size 3 MB
Publisher Microsoft LLC
Product Microsoft

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

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

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Wacatac.

Timeline

First seen 2022-05-13 23:25:58 (3 years ago); latest analysis 2025-10-15 23:00:28 (7 months ago).

Publisher context

Company metadata: Microsoft LLC. Product metadata: Microsoft.

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.

IntelSvc.exe is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft. The reported company name is Microsoft LLC. The current detection status is Trojan.Wacatac, based on the latest analysis from 2025-10-15 23:00:28 (7 months ago).

If IntelSvc.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.Wacatac.

Product Name: Microsoft
Company Name: Microsoft LLC
MD5: a7cde18f991e97037a7899b7669e2548
Size: 3 MB
First Published: 2022-05-13 23:25:58 (3 years ago)
Latest Published: 2025-10-15 23:00:28 (7 months ago)
Status: Trojan.Wacatac (on last analysis)
Analysis Date: 2025-10-15 23:00:28 (7 months ago)
IntelSvc.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.

%windir%
%system%
%windir%
%commonappdata%
%windir%
%commonappdata%
%system%
%system%
%windir%
%localappdata%

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

94.4%
5.6%

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

Windows 10 94.4%
Windows 7 5.6%

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

IntelSvc.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: 0x0018b285

PE Sections:

Name Size of data MD5
.text 1986560 2a1021747144b0683606023555ee43f1
.rdata 361472 7c19d1cc6c83f679695832b158a6a7af
.data 630784 800255788bdb57f9816d8faa03f57aab
.rsrc 148480 66e209adb406d66caa1875bf90997936
.reloc 100864 42c9b97d4919e27829f84976255a88b6

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: