GridinSoft Threat Intelligence

CleanTip.tpi file report

Under review File reputation report
MD5 7fcee9bc872f21e837cee98b9f02a9c8
Latest seen 2024-11-05 23:01:43 (2 years ago)
First seen 2024-11-05 23:01:43 (2 years ago)
Size 1 MB
Publisher www.ludashi.com
Product 鲁大师

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-11-05 23:01:43 (2 years ago); latest analysis 2024-11-05 23:01:43 (2 years ago).

Publisher context

Company metadata: www.ludashi.com. Product metadata: 鲁大师.

Digital signature

Signed by 成都奇鲁科技有限公司. 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.

CleanTip.tpi is a Windows file recorded in the ThreatInfo database. It is associated with 鲁大师. The reported company name is www.ludashi.com. The current detection status is Undefined, based on the latest analysis from 2024-11-05 23:01:43 (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: 鲁大师
Company Name: www.ludashi.com
MD5: 7fcee9bc872f21e837cee98b9f02a9c8
Size: 1 MB
First Published: 2024-11-05 23:01:43 (2 years ago)
Latest Published: 2024-11-05 23:01:43 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-11-05 23:01:43 (2 years ago)
Signed By: 成都奇鲁科技有限公司
Status: Valid

The signature on CleanTip.tpi 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%\ludashi

ThreatInfo has observed CleanTip.tpi 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 10 100.0%

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

CleanTip.tpi is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x000319b7
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1278976

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

.text 646656 bytes · 50.6% of section data
MD5 ba43eec0b1acd4c36b3274076e3d4ab3
.rdata 194048 bytes · 15.2% of section data
MD5 e19ca22d9f980b31212b50bc1fc909cf
.data 21504 bytes · 1.7% of section data
MD5 6abebb1d80183cc876d853aa51bfd2b0
.rsrc 381440 bytes · 29.8% of section data
MD5 29c8c7720d1be8283d96fad1d577c9a2
.reloc 35328 bytes · 2.8% of section data
MD5 8af2daa3452437322c3628fde2f4167e

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