GridinSoft Threat Intelligence

file4[1].exe file report

Clean record File reputation report
MD5 d510c81b25f078bddb705e59052607a9
Latest seen 2021-12-28 21:43:23 (4 years ago)
First seen 2021-12-28 21:43:23 (4 years ago)
Size 801 KB
Publisher kkSljrfwf
Product szQLuRq

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-12-28 21:43:23 (4 years ago); latest analysis 2021-12-28 21:43:23 (4 years ago).

Publisher context

Company metadata: kkSljrfwf. Product metadata: szQLuRq.

Digital signature

Signed by Microsoft 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.

file4[1].exe is a Windows file recorded in the ThreatInfo database. It is associated with szQLuRq. The reported company name is kkSljrfwf. The current detection status is Clean, based on the latest analysis from 2021-12-28 21:43:23 (4 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: szQLuRq
Company Name: kkSljrfwf
MD5: d510c81b25f078bddb705e59052607a9
Size: 801 KB
First Published: 2021-12-28 21:43:23 (4 years ago)
Latest Published: 2021-12-28 21:43:23 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-12-28 21:43:23 (4 years ago)
Signed By: Microsoft 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.

%localappdata%\microsoft\windows\temporary internet files\content.ie5

ThreatInfo has observed file4[1].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 7 100.0%

The most common operating system signal for file4[1].exe is Windows 7 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.

file4[1].exe is identified as pe for 32-bit 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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x000c79ce
Image base 0x00400000

.NET Info:

MVID: 67f2d939-cd2d-40cb-9f1d-eac0e5efa903
Typelib ID: 08f35d3f-37f5-41d2-b7d3-d58a13473b93

PE Sections:

Sections 3
Raw data 811520

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

.text 809472 bytes · 99.7% of section data
MD5 009228f12e8d36f5ce3d5030ff1e0211
.rsrc 1536 bytes · 0.2% of section data
MD5 4ad75dc6cb4705d41d8657612c2f0e2c
.reloc 512 bytes · 0.1% of section data
MD5 1b2aeecddb71b5904cb8e9da6beab594

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 d510c81b25f078bddb705e59052607a9.
  • 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.