GridinSoft Threat Intelligence

tt-service.exe file report

Under review File reputation report
MD5 7d291b84f6d36543cefb79d2452d34c5
Latest seen 2021-01-06 21:46:24 (5 years ago)
First seen 2021-01-06 21:46:24 (5 years ago)
Size 1 MB
Product Telamon Cleaner
Signed by SKARABEI, OOO

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-06 21:46:24 (5 years ago); latest analysis 2021-01-06 21:46:24 (5 years ago).

Publisher context

Product metadata: Telamon Cleaner.

Digital signature

Signed by SKARABEI, OOO. 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. 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.

tt-service.exe is a Windows file recorded in the ThreatInfo database. It is associated with Telamon Cleaner. The current detection status is Undefined, based on the latest analysis from 2021-01-06 21:46:24 (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.

Product Name: Telamon Cleaner
MD5: 7d291b84f6d36543cefb79d2452d34c5
Size: 1 MB
First Published: 2021-01-06 21:46:24 (5 years ago)
Latest Published: 2021-01-06 21:46:24 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-06 21:46:24 (5 years ago)
Signed By: SKARABEI, OOO
Status: Valid

The signature on tt-service.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.

%commonappdata%

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

Windows Embedded Standard 100.0%

The most common operating system signal for tt-service.exe is Windows Embedded Standard 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.

tt-service.exe is identified as pe for 32-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows CUI
Entry point 0x000d1c18
Image base 0x00400000

PE Sections:

Sections 5
Raw data 1204224

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

.text 1007104 bytes · 83.6% of section data
MD5 0ae3fabe94024414d3c35f5de30b356a
.rdata 140288 bytes · 11.6% of section data
MD5 37fb7d39b6abce4121ee30cfa9fa0e14
.data 17408 bytes · 1.4% of section data
MD5 02df4055af7ae328c825e5d38d24f640
.rsrc 1536 bytes · 0.1% of section data
MD5 a244d1de9050c0286d836962c44aca2d
.reloc 37888 bytes · 3.1% of section data
MD5 6b00201cd232bff074f3b441e76b8c28

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 7d291b84f6d36543cefb79d2452d34c5.
  • 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.