ROMServer.exe threat report

MD5 22b891c4191360b8400f9ebc40fb86bc
Latest seen 2021-12-31 21:08:28 (4 years ago)
First seen 2019-08-10 23:04:45 (6 years ago)
Size 6 MB
Product ROMServer

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-12-31 21:08:28 (4 years ago)
File hash
22b891c4191360b8400f9ebc40fb86bc
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Risk.RemoteAdmin.

Timeline

First seen 2019-08-10 23:04:45 (6 years ago); latest analysis 2021-12-31 21:08:28 (4 years ago).

Publisher context

Product metadata: ROMServer.

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.

ROMServer.exe is a Windows file recorded in the ThreatInfo database. It is associated with ROMServer. The current detection status is Risk.RemoteAdmin, based on the latest analysis from 2021-12-31 21:08:28 (4 years ago).

If ROMServer.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: ROMServer
MD5: 22b891c4191360b8400f9ebc40fb86bc
Size: 6 MB
First Published: 2019-08-10 23:04:45 (6 years ago)
Latest Published: 2021-12-31 21:08:28 (4 years ago)
Status: Risk.RemoteAdmin (on last analysis)
Analysis Date: 2021-12-31 21:08:28 (4 years ago)
ROMServer.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 ROMServer.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%
%programfiles%
%programfiles%
%sysdrive%\ammyadmin
%programfiles%
%programfiles%
%programfiles%

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

71.4%
14.3%
7.1%
7.1%

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

Windows 10 57.1%
Windows 7 42.9%

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

ROMServer.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: 0x004ebe74

PE Sections:

Name Size of data MD5
.text 5142016 052a049663b4342c0dd158b73aa72670
.itext 12288 80966f501e40dae8dbae1f797eb42bfe
.data 80384 b1f025d584d4d43efe0fd1cf17de2eb4
.bss 0 00000000000000000000000000000000
.idata 19456 d3bc575e87eb668096394cee713733e7
.didata 3072 82d8da113f988acfc876f100132da32d
.edata 512 4250293a6d53c92d30f21b10b621c955
.tls 0 00000000000000000000000000000000
.rdata 512 c47d861fac80bfa1a61ef8c9147596cb
.reloc 429056 5916da03e717530923dc504322edc1ec
.rsrc 1531904 f6aeab74e142a1604ec75bd92f14dc55

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: