GridinSoft Threat Intelligence

Installer.exe file report

Under review File reputation report
MD5 cbf9d0532e91d44824df2e7b1045138d
Latest seen 2021-03-22 21:21:21 (5 years ago)
First seen 2017-05-27 20:01:57 (9 years ago)
Size 10 MB
Signed by Linkury Ltd

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Category context

Programs that inject advertising, change browser behavior, or monetize traffic through bundled components. Related Adware reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2017-05-27 20:01:57 (9 years ago); latest analysis 2021-03-22 21:21:21 (5 years ago).

Digital signature

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

Installer.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-03-22 21:21:21 (5 years ago). ThreatInfo groups this verdict with Adware reports for broader family-level investigation.

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.

MD5: cbf9d0532e91d44824df2e7b1045138d
Size: 10 MB
First Published: 2017-05-27 20:01:57 (9 years ago)
Latest Published: 2021-03-22 21:21:21 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-03-22 21:21:21 (5 years ago)
Signed By: Linkury Ltd
Status: Valid

The signature on Installer.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%\rheng\46df90b22a534351ad3ca787c51ae9cd
%appdata%\rheng
%sysdrive%\adwcleaner\quarantine\c\users\dist\appdata\roaming\opencandy

ThreatInfo has observed Installer.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 66.7%
Windows 7 33.3%

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

Installer.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 0x0000b01f
Image base 0x4f400000

PE Sections:

Sections 5
Raw data 10480128

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

.text 97280 bytes · 0.9% of section data
MD5 139fa0049b75d6c1e1d4a32c704d8eaf
.rdata 27648 bytes · 0.3% of section data
MD5 453f5e7e6f09f01cf643715d905f702f
.data 5632 bytes · 0.1% of section data
MD5 94a1600f863e67c229e75746b2e4a471
.rsrc 10341888 bytes · 98.7% of section data
Large raw data
MD5 5de5c78bb738c8d632c8303660611043
.reloc 7680 bytes · 0.1% of section data
MD5 5d9f67fcca7ee9bbc8634ee0115474e9

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 cbf9d0532e91d44824df2e7b1045138d.
  • 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. Use the Adware category to compare similar reports.