GridinSoft Threat Intelligence

JECAEHJJJK.exe file report

Clean record File reputation report
MD5 a8fef7b198fa122ead5bcf5b84f2737b
Latest seen 2024-09-08 23:02:07 (2 years ago)
First seen 2024-09-08 23:02:06 (2 years ago)
Size 283 KB
Signed by NVIDIA Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-09-08 23:02:06 (2 years ago); latest analysis 2024-09-08 23:02:07 (2 years ago).

Publisher context

Company metadata: deacidifies infinitively succeeded. Product metadata: mismatching premiership.

Digital signature

Signed by NVIDIA Corporation. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

JECAEHJJJK.exe is a Windows file recorded in the ThreatInfo database. It is associated with mismatching premiership. The reported company name is deacidifies infinitively succeeded. The current detection status is Clean, based on the latest analysis from 2024-09-08 23:02:07 (2 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: mismatching premiership
Company Name: deacidifies infinitively succeeded
MD5: a8fef7b198fa122ead5bcf5b84f2737b
Size: 283 KB
First Published: 2024-09-08 23:02:06 (2 years ago)
Latest Published: 2024-09-08 23:02:07 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-09-08 23:02:07 (2 years ago)
Signed By: NVIDIA Corporation
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%commonappdata%
%profile%\onedrive\documentos

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

Windows 10 100.0%

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

JECAEHJJJK.exe is identified as pe for 32-bit 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.

Format pe
Architecture 32-bit
Subsystem Windows CUI
Entry point 0x00045aae
Image base 0x00400000

.NET Info:

MVID: c75033bb-52dc-4d44-8cb6-fc3643f03f99
Typelib ID: 375c5eff-0650-4301-85ef-382cfefa9adf

PE Sections:

Sections 3
Raw data 280064

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 277504 bytes · 99.1% of section data
MD5 2a588a396f9ea2b615b421f3e7a4a4e7
.rsrc 2048 bytes · 0.7% of section data
MD5 92ed0a92aac0c624ee743a961e740ca7
.reloc 512 bytes · 0.2% of section data
MD5 0f3b946f6eb64335593a5c511673bedb

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.

Report conclusion

This hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with a8fef7b198fa122ead5bcf5b84f2737b.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.