ROMFUSClient.exe threat report

MD5 b26f60f0e52c86b2a523cf6aca661dfd
Latest seen 2021-01-06 06:10:16 (5 years ago)
First seen 2019-03-07 02:08:40 (7 years ago)
Size 5 MB
Product ROMFUSClient

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Risk.RemoteAdmin. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Risk.RemoteAdmin
Recommended action
Scan and remove
Last analysis
2021-01-06 06:10:16 (5 years ago)
File hash
b26f60f0e52c86b2a523cf6aca661dfd
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Risk.RemoteAdmin.

Timeline

First seen 2019-03-07 02:08:40 (7 years ago); latest analysis 2021-01-06 06:10:16 (5 years ago).

Publisher context

Product metadata: ROMFUSClient.

Digital signature

Signed by Yakhnovets Denis Aleksandrovich IP. 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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

ROMFUSClient.exe is a Windows file recorded in the ThreatInfo database. It is associated with ROMFUSClient. The current detection status is Risk.RemoteAdmin, based on the latest analysis from 2021-01-06 06:10:16 (5 years ago).

If ROMFUSClient.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Risk.RemoteAdmin.

Product Name: ROMFUSClient
MD5: b26f60f0e52c86b2a523cf6aca661dfd
Size: 5 MB
First Published: 2019-03-07 02:08:40 (7 years ago)
Latest Published: 2021-01-06 06:10:16 (5 years ago)
Status: Risk.RemoteAdmin (on last analysis)
Analysis Date: 2021-01-06 06:10:16 (5 years ago)
ROMFUSClient.exe detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

Signed By: Yakhnovets Denis Aleksandrovich IP
Status: Valid

The signature on ROMFUSClient.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.

%programfiles%\litemanager pro - viewer
%programfiles%\litemanager pro - viewer
%programfiles%
%programfiles%
%programfiles%\litemanager pro - viewer
%programfiles%
%programfiles%
%sysdrive%\windows.old\program files (x86)\litemanager pro - viewer
%programfiles%
%programfiles%

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

77.4%
6.0%
6.0%
4.8%
2.4%
1.2%
1.2%
1.2%

The strongest geographic signal for this file is Germany with 77.4% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 88.1%
Windows 7 6.0%
Windows Server 2016 4.8%
Windows 8.1 1.2%

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

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

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x00400000
Entry Address: 0x003ebdb0

PE Sections:

Name Size of data MD5
.text 4096000 1d2adb2cc630c2d91df64b153876dec4
.itext 12288 33db37eeb25b0cdf0d8892aa05b015b1
.data 76800 f05bc38979b25830b48e18509500a71b
.bss 0 00000000000000000000000000000000
.idata 16896 d4dec98a82e0d74157491013679279f2
.didata 3072 1167237ab215dbfdd306f9f7f24b1603
.edata 512 b09e5b2862b126d86fa87f69bd0267b6
.tls 0 00000000000000000000000000000000
.rdata 512 c10e1405cf51f13707ff26639cf9564b
.reloc 358400 68bfc6c0b0590ca9c3c5c26e72362e41
.rsrc 1251840 215b43f47c7754c183dc0b060aefc4bb

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.

More information: