GridinSoft Threat Intelligence

pskill.exe file report

Clean record File reputation report
MD5 b5891462c9ca5bddfe63d3bae3c14e0b
Latest seen 2023-07-11 23:45:24 (2 years ago)
First seen 2017-11-08 10:08:03 (8 years ago)
Size 457 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-11-08 10:08:03 (8 years ago); latest analysis 2023-07-11 23:45:24 (2 years ago).

Publisher context

Company metadata: Sysinternals - www.sysinternals.com. Product metadata: Sysinternals pkill.

Digital signature

Signed by Microsoft Corporation. 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. 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.

pskill.exe is a Windows file recorded in the ThreatInfo database. It is associated with Sysinternals pkill. The reported company name is Sysinternals - www.sysinternals.com. The current detection status is Clean, based on the latest analysis from 2023-07-11 23:45:24 (2 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.

Product Name: Sysinternals pkill
Company Name: Sysinternals - www.sysinternals.com
MD5: b5891462c9ca5bddfe63d3bae3c14e0b
Size: 457 KB
First Published: 2017-11-08 10:08:03 (8 years ago)
Latest Published: 2023-07-11 23:45:24 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-07-11 23:45:24 (2 years ago)
Signed By: Microsoft Corporation
Status: Valid

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

%profile%
%programfiles%\easyphp-devserver-17

ThreatInfo has observed pskill.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 7 50.0%
Windows 10 50.0%

The most common operating system signal for pskill.exe is Windows 7 with 50.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.

pskill.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 0x0000743d
Image base 0x00400000

PE Sections:

Sections 4
Raw data 460800

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

.text 116736 bytes · 25.3% of section data
MD5 04d6e5e257e7928a37babe4f32a01771
.rdata 26624 bytes · 5.8% of section data
MD5 1422a0f3235b33e69cbba4d4ee3b980a
.data 4608 bytes · 1.0% of section data
MD5 9a85a1c76a5e24927ef23ae4042e537f
.rsrc 312832 bytes · 67.9% of section data
MD5 d29165b697b8ba35145686e64d312269

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