GridinSoft Threat Intelligence

A56K1.exe file report

Clean record File reputation report
MD5 b5d46f379fab753a05137a89bab72857
Latest seen 2022-05-18 23:15:02 (4 years ago)
First seen 2022-05-06 23:25:23 (4 years ago)
Size 758 KB
Product VH Video SDK
Signed by Razer USA Ltd.

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-05-06 23:25:23 (4 years ago); latest analysis 2022-05-18 23:15:02 (4 years ago).

Publisher context

Company metadata: SplitmediaLabs Limited. Product metadata: VH Video SDK.

Digital signature

Signed by Razer USA Ltd.. 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.

A56K1.exe is a Windows file recorded in the ThreatInfo database. It is associated with VH Video SDK. The reported company name is SplitmediaLabs Limited. The current detection status is Clean, based on the latest analysis from 2022-05-18 23:15:02 (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: VH Video SDK
Company Name: SplitmediaLabs Limited
MD5: b5d46f379fab753a05137a89bab72857
Size: 758 KB
First Published: 2022-05-06 23:25:23 (4 years ago)
Latest Published: 2022-05-18 23:15:02 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-05-18 23:15:02 (4 years ago)
Signed By: Razer USA Ltd.
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.

%temp%

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

A56K1.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 0x00088000
Image base 0x00400000

PE Sections:

Sections 4
Raw data 767908

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

CODE 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
CODE 512 bytes · 0.1% of section data
MD5 3497040ffdaff5c3fc86dba736209738
.rsrc 349900 bytes · 45.6% of section data
MD5 5841bb77b9fd6202080a1ead6b7a6958
.rdata 417496 bytes · 54.4% of section data
MD5 2392ab7f70b9b32c5da0b5ac6b9fec75

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