GridinSoft Threat Intelligence

Honeygain.exe file report

Under review File reputation report
MD5 5a25344a89b67d159aa8a67b9b340394
Latest seen 2022-06-25 23:28:30 (3 years ago)
First seen 2022-06-25 23:28:30 (3 years ago)
Size 954 KB
Product Honeygain
Signed by OOO "XMAC"

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-06-25 23:28:30 (3 years ago); latest analysis 2022-06-25 23:28:30 (3 years ago).

Publisher context

Product metadata: Honeygain.

Digital signature

Signed by OOO "XMAC". The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

Honeygain.exe is a Windows file recorded in the ThreatInfo database. It is associated with Honeygain. The current detection status is Undefined, based on the latest analysis from 2022-06-25 23:28:30 (3 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: Honeygain
MD5: 5a25344a89b67d159aa8a67b9b340394
Size: 954 KB
First Published: 2022-06-25 23:28:30 (3 years ago)
Latest Published: 2022-06-25 23:28:30 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-06-25 23:28:30 (3 years ago)
Signed By: OOO "XMAC"
Status: Valid

The signature on Honeygain.exe is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%appdata%

ThreatInfo has observed Honeygain.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 8.1 100.0%

The most common operating system signal for Honeygain.exe is Windows 8.1 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.

Honeygain.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 0x000e467a
Image base 0x00400000

.NET Info:

MVID: bb29e838-d037-4378-93ab-782c2c6e1b2e
Typelib ID: a48ab92d-a4d2-4a4d-8150-bfeaa6508f33

PE Sections:

Sections 3
Raw data 969216

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

.text 927744 bytes · 95.7% of section data
MD5 163b105a47859de382b0582e48ba4ea9
.rsrc 40960 bytes · 4.2% of section data
MD5 586d1b31cdc91379a33757b73322fbd9
.reloc 512 bytes · 0.1% of section data
MD5 9fa696911fd9d9c22a143425f2f0f517

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 5a25344a89b67d159aa8a67b9b340394.
  • 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.