GridinSoft Threat Intelligence

Splash.exe file report

Under review File reputation report
MD5 ecc28a0bcf3f1740bac032164d4eef56
Latest seen 2024-10-15 23:06:54 (2 years ago)
First seen 2024-09-27 23:04:39 (2 years ago)
Size 1 MB
Publisher RealDefense LLC
Product MyCleanPC
Signed by RealDefense LLC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-09-27 23:04:39 (2 years ago); latest analysis 2024-10-15 23:06:54 (2 years ago).

Publisher context

Company metadata: RealDefense LLC. Product metadata: MyCleanPC.

Digital signature

Signed by RealDefense LLC. 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.

Splash.exe is a Windows file recorded in the ThreatInfo database. It is associated with MyCleanPC. The reported company name is RealDefense LLC. The current detection status is Undefined, based on the latest analysis from 2024-10-15 23:06:54 (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: MyCleanPC
Company Name: RealDefense LLC
MD5: ecc28a0bcf3f1740bac032164d4eef56
Size: 1 MB
First Published: 2024-09-27 23:04:39 (2 years ago)
Latest Published: 2024-10-15 23:06:54 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-10-15 23:06:54 (2 years ago)
Signed By: RealDefense LLC
Status: Valid

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

%programfiles%

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

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

Splash.exe 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 0x000e6222
Image base 0x00400000

.NET Info:

MVID: ab3ca7b3-efcc-4832-b38e-986f9b176e12
Typelib ID: 1bb72429-a87e-438c-bb55-5b019f4e929e

PE Sections:

Sections 3
Raw data 1056768

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

.text 934912 bytes · 88.5% of section data
MD5 0cbb8051e413feb91c2133a13c9b93e7
.reloc 512 bytes · 0.0% of section data
MD5 56b5a54ba0d76c3a4633593ae621a03e
.rsrc 121344 bytes · 11.5% of section data
MD5 2edef8e25463b17589c442e19c1cb9bc

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