Telegram.exe file report

MD5 34a4e9bbfa966fba81bbf735faab7941
Latest seen 2023-07-15 23:40:36 (2 years ago)
First seen 2023-07-15 23:40:36 (2 years ago)
Size 25 MB
Publisher Telegram FZ-LLC

This report summarizes the file identity, detection status, publisher metadata, observed locations, and technical indicators for Telegram.exe. ThreatInfo does not have a final classification for this sample yet.

Telegram.exe is a Windows file recorded in the ThreatInfo database. It is associated with Telegram Desktop . The reported company name is Telegram FZ-LLC . The current detection status is Undefined, based on the latest analysis from 2023-07-15 23:40:36 (2 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.

Product Name: Telegram Desktop
Company Name: Telegram FZ-LLC
MD5: 34a4e9bbfa966fba81bbf735faab7941
Size: 25 MB
First Published: 2023-07-15 23:40:36 (2 years ago)
Latest Published: 2023-07-15 23:40:36 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-07-15 23:40:36 (2 years ago)
%appdata%\driverpack cloud

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

Telegram.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: 0x000b5eec

PE Sections:

Name Size of data MD5
.text 735232 ad6e46e3a3acdb533eb6a077f6d065af
.itext 6144 d40fc822339d01f2abcc5493ac101c94
.data 14336 4c195d5591f6d61265df08a3733de3a2
.bss 0 d41d8cd98f00b204e9800998ecf8427e
.idata 4096 a73d686f1e8b9bb06ec767721135e397
.didata 512 41b8ce23dd243d14beebc71771885c89
.edata 512 37c1a5c63717831863e018c0f51dabb7
.tls 0 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 8f2f090acd9622c88a6a852e72f94e96
.rsrc 383488 a94f7f8719f9a1219e34d4f77adff76a

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: