PhotoRenamer.exe threat report

MD5 f276c5d3d72c197a5cbaa5eea3539eb3
Latest seen 2023-01-02 23:54:10 (3 years ago)
First seen 2023-01-02 23:53:56 (3 years ago)
Size 4 MB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. 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
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2023-01-02 23:54:10 (3 years ago)
File hash
f276c5d3d72c197a5cbaa5eea3539eb3
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2023-01-02 23:53:56 (3 years ago); latest analysis 2023-01-02 23:54:10 (3 years ago).

Publisher context

Company metadata: Acronis International GmbH.. Product metadata: Acronis Files Connect.

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.

PhotoRenamer.exe is a Windows file recorded in the ThreatInfo database. It is associated with Acronis Files Connect. The reported company name is Acronis International GmbH.. The current detection status is Trojan.Heur!, based on the latest analysis from 2023-01-02 23:54:10 (3 years ago).

If PhotoRenamer.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 Trojan.Heur!.

Product Name: Acronis Files Connect
Company Name: Acronis International GmbH.
MD5: f276c5d3d72c197a5cbaa5eea3539eb3
Size: 4 MB
First Published: 2023-01-02 23:53:56 (3 years ago)
Latest Published: 2023-01-02 23:54:10 (3 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2023-01-02 23:54:10 (3 years ago)
PhotoRenamer.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.

%programfiles%
%programfiles%

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

100.0%

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

Windows 10 100.0%

The most common operating system signal for PhotoRenamer.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.

PhotoRenamer.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: 0x00001084

PE Sections:

Name Size of data MD5
.text 2432512 c4477ec844850b485eeee696e2109a0a
.data 10752 57f7f584be7453f8f0fa722f5a4bd67b
.tls 5120 e1fd87bd40a997db6d6a3f21f24c4f57
.34850 512 eae1a3b5bdd3b75592813a140cfabbce
.idata 17408 8670c13e180ddf7b7fce4c1ba0d4fa54
.rsrc 3072 8e95eda240a6b6a9dad90a8fa7940356
.34852 2252781 517bd891ec00d59212716058f71ef958

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: