FreeCommander.exe threat report

MD5 e288b54b4a0adea5742f958cc5c4d21d
Latest seen 2023-12-27 23:59:19 (2 years ago)
First seen 2023-12-27 23:59:19 (2 years ago)
Size 19 MB
Publisher Marek Jasinski
Signed by Marek Jasinski

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as General Threat. 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
General Threat
Recommended action
Scan and remove
Last analysis
2023-12-27 23:59:19 (2 years ago)
File hash
e288b54b4a0adea5742f958cc5c4d21d
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as General Threat.

Timeline

First seen 2023-12-27 23:59:19 (2 years ago); latest analysis 2023-12-27 23:59:19 (2 years ago).

Publisher context

Company metadata: Marek Jasinski. Product metadata: FreeCommander XE.

Digital signature

Signed by Marek Jasinski. 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.

FreeCommander.exe is a Windows file recorded in the ThreatInfo database. It is associated with FreeCommander XE. The reported company name is Marek Jasinski. The current detection status is General Threat, based on the latest analysis from 2023-12-27 23:59:19 (2 years ago).

If FreeCommander.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 General Threat.

Product Name: FreeCommander XE
Company Name: Marek Jasinski
MD5: e288b54b4a0adea5742f958cc5c4d21d
Size: 19 MB
First Published: 2023-12-27 23:59:19 (2 years ago)
Latest Published: 2023-12-27 23:59:19 (2 years ago)
Status: General Threat (on last analysis)
Analysis Date: 2023-12-27 23:59:19 (2 years ago)
FreeCommander.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: Marek Jasinski
Status: Valid

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

ThreatInfo has observed FreeCommander.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 United Kingdom 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 FreeCommander.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.

FreeCommander.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: 0x00e337a8

PE Sections:

Name Size of data MD5
.text 14860800 8fbe6c8994bffbe4780aa610e23f6d01
.itext 24064 f32156dcfbdb0de7da237a4330308485
.data 381440 04ed11d4318042410a23a925b2a67cf6
.bss 0 d41d8cd98f00b204e9800998ecf8427e
.idata 28160 26b204a1dae30882369ef22feba83961
.didata 3584 97dc081c9f864f79b87ce6eb1fc88039
.edata 512 73d74a4deb820c36335370065bc3fabf
.tls 0 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 2817f99c7b1792a51422fa437cc6e376
.reloc 900608 5a4400e47ba09233af42609369e31912
.rsrc 4163584 2f7c699615e4e7b33655c4249fbbd414

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: