GoogleDriveFS.exe threat report

MD5 20396e75f8c07ae56476df26dfc00df4
Latest seen 2024-10-05 23:01:22 (2 years ago)
First seen 2024-10-05 23:01:22 (2 years ago)
Size 58 MB
Publisher Google, Inc.
Product Google Drive

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
2024-10-05 23:01:22 (2 years ago)
File hash
20396e75f8c07ae56476df26dfc00df4
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2024-10-05 23:01:22 (2 years ago); latest analysis 2024-10-05 23:01:22 (2 years ago).

Publisher context

Company metadata: Google, Inc.. Product metadata: Google Drive.

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.

GoogleDriveFS.exe is a Windows file recorded in the ThreatInfo database. It is associated with Google Drive. The reported company name is Google, Inc.. The current detection status is Trojan.Heur!, based on the latest analysis from 2024-10-05 23:01:22 (2 years ago).

If GoogleDriveFS.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: Google Drive
Company Name: Google, Inc.
MD5: 20396e75f8c07ae56476df26dfc00df4
Size: 58 MB
First Published: 2024-10-05 23:01:22 (2 years ago)
Latest Published: 2024-10-05 23:01:22 (2 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2024-10-05 23:01:22 (2 years ago)
GoogleDriveFS.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%\google\drive file stream

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

GoogleDriveFS.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: 0x01b6be04

PE Sections:

Name Size of data MD5
.text 29075968 f458c1d141aa316a554a182f65471719
.rdata 23399936 4fdeb700989ce819b780060d07abf505
.data 2714624 3065cda9d8b81c31826b3cdd93242557
.pdata 1758208 83c8fbc3837c566aecbd6fc190831023
.gxfg 15360 a3cd2b6e66b332b625c607cfb9b9359f
.retplne 512 78aee4736480fa27c1a718e1f3aadb89
.tls 512 dafc6b46862467c08fc17d94897fcfa3
CPADinfo 512 60d3ea61d541c9be2e845d2787fb9574
_RDATA 512 9b8a6f3b0166fed6faac5e22e04f1458
flags_he 12288 b7a0aea8465a46a54355382ae3b229dd
google_i 512 e7c16a4176faf09a57cdabf271ab363c
malloc_h 1024 a0c3e4fd726ee3204c1ba24ce47610c1
protodes 1150976 f58d840df57618bf6ce958417dc6c789
.rsrc 2790912 4dd61484ad18e594c944ab8b346d5ce4
.reloc 432128 3ec71233aa14efae6928467f9e1d6185
/4 512 13dc278b7dde0302771fd6e22857c5a2
/18 512 8297bba5e58345b08b4f0cd5782e8213
/33 1024 ba8c20aa05d01a727a3fde0ed145fc59
/45 512 fc1e1431c33463b96ae9b54e77f0f065

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: