service.exe threat report

MD5 bd449f33c7685aaa2191aa351860c387
Latest seen 2021-02-04 16:10:36 (5 years ago)
First seen 2021-02-04 16:10:30 (5 years ago)
Size 6 MB
Publisher Microsoft
Product Microsoft Edge

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. 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.Heur!
Recommended action
Scan and remove
Last analysis
2021-02-04 16:10:36 (5 years ago)
File hash
bd449f33c7685aaa2191aa351860c387
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2021-02-04 16:10:30 (5 years ago); latest analysis 2021-02-04 16:10:36 (5 years ago).

Publisher context

Company metadata: Microsoft. Product metadata: Microsoft Edge.

Digital signature

Signed by Latinose Google LLC. The signature is reported as valid, but signed files can still be bundled or abused.

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.

service.exe is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft Edge. The reported company name is Microsoft. The current detection status is Trojan.Heur!, based on the latest analysis from 2021-02-04 16:10:36 (5 years ago).

If service.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.Heur!.

Product Name: Microsoft Edge
Company Name: Microsoft
MD5: bd449f33c7685aaa2191aa351860c387
Size: 6 MB
First Published: 2021-02-04 16:10:30 (5 years ago)
Latest Published: 2021-02-04 16:10:36 (5 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2021-02-04 16:10:36 (5 years ago)
service.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.

Signed By: Latinose Google LLC
Status: Valid

The signature on service.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.

%appdata%
%temp%

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

Windows 10 100.0%

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

service.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: 0x007c1efa

PE Sections:

Name Size of data MD5
8704 8d8f3e27f239bdf912cbcabfb16e138f
512 15b59aab73bf65919f634091127e59a8
512 40edf55cb40a4ec7dd08a0b0c4ab4bb6
1536 80054020203295ca20a40b7d04fb51b4
0 d41d8cd98f00b204e9800998ecf8427e
512 db6879be295b77c9338ad9cfe5e4282f
512 b811fcacc74ba12edd26503b2491123e
512 d676cfa4b897887140d99bb658a80cd0
.vmp0 197120 b6837e3b36f08091f41a679e9a1278ff
.idata 512 7bb74db5d4910eaa3574e317e006d598
.tls 512 4c0017b59f2582573dc757e01d10a824
.themida 0 d41d8cd98f00b204e9800998ecf8427e
.boot 2073088 92ceca89581e31b74f4053ac60952e30
.vmp0 2443264 74091f499d2d47d1e992637134eec447
.vmp1 1925632 6fa1e40859f122febbe7b049ed95fc8b
.rsrc 165376 693f0fa9669140e09bb3fb0b76f832ef

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: