ltr.exe threat report

MD5 8e700b4f7f4e9d773edc1d72aaede656
Latest seen 2025-05-11 23:01:11 (a year ago)
First seen 2024-02-17 23:11:29 (2 years ago)
Size 18 MB
Publisher Loaris Inc.
Signed by "Loaris" LLC

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Agent. 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.Agent
Recommended action
Scan and remove
Last analysis
2025-05-11 23:01:11 (a year ago)
File hash
8e700b4f7f4e9d773edc1d72aaede656
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Agent.

Timeline

First seen 2024-02-17 23:11:29 (2 years ago); latest analysis 2025-05-11 23:01:11 (a year ago).

Publisher context

Company metadata: Loaris Inc.. Product metadata: Loaris Trojan Remover.

Digital signature

Signed by "Loaris" LLC. The signature is not reported as trusted and valid, which can indicate tampering, repackaging, or copied publisher data.

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.

ltr.exe is a Windows file recorded in the ThreatInfo database. It is associated with Loaris Trojan Remover. The reported company name is Loaris Inc.. The current detection status is Trojan.Agent, based on the latest analysis from 2025-05-11 23:01:11 (a year ago).

If ltr.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.Agent.

Product Name: Loaris Trojan Remover
Company Name: Loaris Inc.
MD5: 8e700b4f7f4e9d773edc1d72aaede656
Size: 18 MB
First Published: 2024-02-17 23:11:29 (2 years ago)
Latest Published: 2025-05-11 23:01:11 (a year ago)
Status: Trojan.Agent (on last analysis)
Analysis Date: 2025-05-11 23:01:11 (a year ago)
ltr.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: "Loaris" LLC
Status: Invalid (digital signature could be stolen or file could be patched)

The signature on ltr.exe is not reported as trusted and valid. Invalid or suspicious signature data can indicate tampering, repackaging, or an unrelated file using copied publisher information.

%desktop%\loaris.trojan.remover.3.2.81.1856.portable\loaris trojan remover 3.2.81.1856 portable\app
%programfiles%
%programfiles%
%sysdrive%\downloads\[ftuapps.com] - loaris trojan remover v3.2.81.1856 (x64) multilingual portable\loaris trojan remover 3.2.81.1856 portable\app
%programfiles%

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

60.0%
20.0%
20.0%

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

Windows 10 80.0%
Windows 7 20.0%

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

ltr.exe is identified as pe for 64 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: 64
Image Base: 0x0000000000400000
Entry Address: 0x00c2bab0

PE Sections:

Name Size of data MD5
.text 12941312 0a814ae1440aad2e4ec03894215dfb01
.data 1187328 11a8efe8fa51fbd834d9b924c301604f
.bss 0 d41d8cd98f00b204e9800998ecf8427e
.idata 49664 37a3f0a0866eac074ab441ce0421cdcc
.didata 6144 a638fb9d2d3ad3cc91bdf2d69ff54f68
.edata 512 96a3ba2fad6b79f672225a8439e0b9b1
.tls 0 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 5ebd4fea078ef2ede8247d63e6582cd1
.reloc 605696 5452b109473ebf5aef03ee11fc442c93
.pdata 661504 fc025a597f06942baa885d66cef6113e
.rsrc 3938816 08a0bc8d4618fa5e8639b0ba72615c48

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: