GridinSoft Threat Intelligence

5380.exe file report

Under review File reputation report
MD5 1060dab922e98eafe6883e1a00cd0eb8
Latest seen 2022-04-28 23:42:49 (4 years ago)
First seen 2022-04-22 23:09:45 (4 years ago)
Size 2 MB
Publisher Moonsworth, LLC
Product Lunar Client
Signed by Nod32 ESET

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-04-22 23:09:45 (4 years ago); latest analysis 2022-04-28 23:42:49 (4 years ago).

Publisher context

Company metadata: Moonsworth, LLC. Product metadata: Lunar Client.

Digital signature

Signed by Nod32 ESET. 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.

5380.exe is a Windows file recorded in the ThreatInfo database. It is associated with Lunar Client. The reported company name is Moonsworth, LLC. The current detection status is Undefined, based on the latest analysis from 2022-04-28 23:42:49 (4 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: Lunar Client
Company Name: Moonsworth, LLC
MD5: 1060dab922e98eafe6883e1a00cd0eb8
Size: 2 MB
First Published: 2022-04-22 23:09:45 (4 years ago)
Latest Published: 2022-04-28 23:42:49 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-04-28 23:42:49 (4 years ago)
Signed By: Nod32 ESET
Status: Valid

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

%temp%
%sysdrive%\$recycle.bin

ThreatInfo has observed 5380.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 66.7%
Windows 7 33.3%

The most common operating system signal for 5380.exe is Windows 10 with 66.7% 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.

5380.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 0x0001badf
Image base 0x00400000

PE Sections:

Sections 4
Raw data 151552

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

.text 112128 bytes · 74.0% of section data
MD5 5cd9e7e9a0ddc56f3f8a10181cb140fb
.rdata 16896 bytes · 11.1% of section data
MD5 9ee44b06274630b02d679effda37e982
.data 2048 bytes · 1.4% of section data
MD5 ac517e5404c5c361270416128d77c7fb
.rsrc 20480 bytes · 13.5% of section data
MD5 def930e25cbf00a6ab6e9f3bba8aaa54

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 1060dab922e98eafe6883e1a00cd0eb8.
  • 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.