GridinSoft Threat Intelligence

ltr.exe file report

Under review File reputation report
MD5 17e801316fe51a8d327809d31a5f0404
Latest seen 2021-01-14 18:53:53 (5 years ago)
First seen 2021-01-14 18:53:53 (5 years ago)
Size 17 MB
Publisher Loaris Inc.
Product Loaris Trojan Remover

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-14 18:53:53 (5 years ago); latest analysis 2021-01-14 18:53:53 (5 years ago).

Publisher context

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

Recommended action

What to do next

  1. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

File context

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 Undefined, based on the latest analysis from 2021-01-14 18:53:53 (5 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

File Details

Product Name: Loaris Trojan Remover
Company Name: Loaris Inc.
MD5: 17e801316fe51a8d327809d31a5f0404
Size: 17 MB
First Published: 2021-01-14 18:53:53 (5 years ago)
Latest Published: 2021-01-14 18:53:53 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-14 18:53:53 (5 years ago)

Geographic signal

Observed country distribution

ThreatInfo has seen ltr.exe across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Russian Federation
Share 100.0%
Low High activity

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.

OS Version:

Windows 10 100.0%

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

Analysis

ltr.exe is identified as pe for 64-bit 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.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x00b347b0
Image base 0x0000000000400000

PE Sections:

Sections 11
Raw data 17907712

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 11921920 bytes · 66.6% of section data
Large raw data
MD5 adb910a2fe5ce9accbab575538154ff8
.data 1095168 bytes · 6.1% of section data
MD5 5b930e02523a4fb7aa041854e3ce4c17
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 49664 bytes · 0.3% of section data
MD5 0ab5e3c880d6110a75b52dc584b996aa
.didata 5632 bytes · 0.0% of section data
Uncommon name
MD5 16d53456462b98d3443b4bc035f61f38
.edata 512 bytes · 0.0% of section data
MD5 43c8bd81af7315fe7735c2a6974d7318
.tls 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 bytes · 0.0% of section data
MD5 abf1740f2972909c752571a4f806d38f
.reloc 558592 bytes · 3.1% of section data
MD5 8012ddb774a267c1b1f4aa0dce488c8c
.pdata 602624 bytes · 3.4% of section data
MD5 59f54f38781ea7ac0f7efc3143c63661
.rsrc 3673088 bytes · 20.5% of section data
MD5 b44ce60a887ffc631578e41e94280086

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.

Report conclusion

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 17e801316fe51a8d327809d31a5f0404.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.