GridinSoft Threat Intelligence

PERV50_WW_WIN_3770_41_S.exe file report

Clean record File reputation report
MD5 ed9fd10fe735e693cee032da052c1bfe
Latest seen 2021-04-11 20:17:04 (5 years ago)
First seen 2020-09-19 06:39:37 (5 years ago)
Size 10 MB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-09-19 06:39:37 (5 years ago); latest analysis 2021-04-11 20:17:04 (5 years ago).

Digital signature

Signed by SEIKO EPSON CORPORATION. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

PERV50_WW_WIN_3770_41_S.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2021-04-11 20:17:04 (5 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

MD5: ed9fd10fe735e693cee032da052c1bfe
Size: 10 MB
First Published: 2020-09-19 06:39:37 (5 years ago)
Latest Published: 2021-04-11 20:17:04 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-04-11 20:17:04 (5 years ago)
Signed By: SEIKO EPSON CORPORATION
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%profile%
%sysdrive%

ThreatInfo has observed PERV50_WW_WIN_3770_41_S.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 Australia 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 PERV50_WW_WIN_3770_41_S.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.

PERV50_WW_WIN_3770_41_S.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 0x0000af1e
Image base 0x00400000

PE Sections:

Sections 5
Raw data 11411456

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

.text 77824 bytes · 0.7% of section data
MD5 cc1d28effbdec11267db3c3abed2d6f4
.rdata 16384 bytes · 0.1% of section data
MD5 0652c0ddd748c5a8a27ed642e547ef6d
.data 8192 bytes · 0.1% of section data
MD5 8c554a07999d93274259ebbc68177a5c
.rsrc 40960 bytes · 0.4% of section data
MD5 05bed5f83fffc1dd04ee8839a181ea3a
_winzip_ 11268096 bytes · 98.7% of section data
Large raw data Uncommon name
MD5 e353dfd514d5a272c5b63a753c281570

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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