GridinSoft Threat Intelligence

salitykiller.exe file report

Clean record File reputation report
MD5 254d1c6306af67014597b52a1fd84ae3
Latest seen 2021-02-25 16:01:59 (5 years ago)
First seen 2021-01-03 03:04:17 (5 years ago)
Size 288 KB
Publisher Kaspersky Lab ZAO
Product SalityKiller
Signed by Kaspersky Lab

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-01-03 03:04:17 (5 years ago); latest analysis 2021-02-25 16:01:59 (5 years ago).

Publisher context

Company metadata: Kaspersky Lab ZAO. Product metadata: SalityKiller.

Digital signature

Signed by Kaspersky Lab. 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.

salitykiller.exe is a Windows file recorded in the ThreatInfo database. It is associated with SalityKiller. The reported company name is Kaspersky Lab ZAO. The current detection status is Clean, based on the latest analysis from 2021-02-25 16:01:59 (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.

Product Name: SalityKiller
Company Name: Kaspersky Lab ZAO
MD5: 254d1c6306af67014597b52a1fd84ae3
Size: 288 KB
First Published: 2021-01-03 03:04:17 (5 years ago)
Latest Published: 2021-02-25 16:01:59 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-25 16:01:59 (5 years ago)
Signed By: Kaspersky Lab
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.

%programfiles%

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

salitykiller.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 0x00002f63
Image base 0x00400000

PE Sections:

Sections 5
Raw data 270848

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

.text 40960 bytes · 15.1% of section data
MD5 e3765b05ffcaf20416185e382bf8fccc
.rdata 13824 bytes · 5.1% of section data
MD5 8ac5a5b602ff3bec4cf6045613ab1859
.data 4096 bytes · 1.5% of section data
MD5 516c10ef593f128dffc57b5a731d1535
.rsrc 206336 bytes · 76.2% of section data
MD5 ff6ef3b0bcc4c259199830620f2dcec1
.reloc 5632 bytes · 2.1% of section data
MD5 eb7c1b0a1849c9a6ebb9c488ea80eb02

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 254d1c6306af67014597b52a1fd84ae3.
  • 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.