native.exe threat report

MD5 76d3d78bd2002c244b4afe6a5fd8e095
Latest seen 2021-07-18 20:44:43 (4 years ago)
First seen 2018-12-05 16:06:58 (7 years ago)
Size 228 KB
Publisher Google Chrome

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
2021-07-18 20:44:43 (4 years ago)
File hash
76d3d78bd2002c244b4afe6a5fd8e095
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Agent.

Timeline

First seen 2018-12-05 16:06:58 (7 years ago); latest analysis 2021-07-18 20:44:43 (4 years ago).

Publisher context

Company metadata: Google Chrome. Product metadata: Browser Crash Handle.

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.

native.exe is a Windows file recorded in the ThreatInfo database. It is associated with Browser Crash Handle. The reported company name is Google Chrome. The current detection status is Trojan.Agent, based on the latest analysis from 2021-07-18 20:44:43 (4 years ago).

If native.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.

Product Name: Browser Crash Handle
Company Name: Google Chrome
MD5: 76d3d78bd2002c244b4afe6a5fd8e095
Size: 228 KB
First Published: 2018-12-05 16:06:58 (7 years ago)
Latest Published: 2021-07-18 20:44:43 (4 years ago)
Status: Trojan.Agent (on last analysis)
Analysis Date: 2021-07-18 20:44:43 (4 years ago)
native.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.

%localappdata%
%localappdata%
%localappdata%
%localappdata%
%localappdata%
%localappdata%
%localappdata%
%localappdata%
%localappdata%
%localappdata%

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

32.4%
29.4%
14.7%
11.8%
8.8%
2.9%

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

Windows 7 45.9%
Windows 10 43.2%
Windows 8.1 10.8%

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

native.exe is identified as pe for 32 systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 32
Image Base: 0x00400000
Entry Address: 0x0000b81d

PE Sections:

Name Size of data MD5
.text 154624 e5586aca4a6ae32ae058ba22158a2f5c
.rdata 61440 cf998ae6be4324a899c7e25ce2830d7d
.data 4096 f20c94429705adaebd8e1e1143f4dfd7
.gfids 1024 9568729c7c43e7f51ed8794d459c5dc8
.tls 512 1f354d76203061bfdd5a53dae48d5435
.rsrc 1536 1149e68e945a2eb2e348637ef2acf10d
.reloc 9216 2b5f1c8766e0eb0b6fd143850d0c3a76

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: