GridinSoft Threat Intelligence

integrity_check_tool.exe file report

Clean record File reputation report
MD5 0cc970f0ec6bd236bf585ead276f62c2
Latest seen 2021-01-07 13:04:32 (5 years ago)
First seen 2020-11-12 08:07:03 (5 years ago)
Size 1 MB
Publisher Kaspersky Lab
Signed by Kaspersky Lab

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-11-12 08:07:03 (5 years ago); latest analysis 2021-01-07 13:04:32 (5 years ago).

Publisher context

Company metadata: Kaspersky Lab. Product metadata: Kaspersky Security for Virtualization 5.1 Light Agent.

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.

integrity_check_tool.exe is a Windows file recorded in the ThreatInfo database. It is associated with Kaspersky Security for Virtualization 5.1 Light Agent. The reported company name is Kaspersky Lab. The current detection status is Clean, based on the latest analysis from 2021-01-07 13:04:32 (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: Kaspersky Security for Virtualization 5.1 Light Agent
Company Name: Kaspersky Lab
MD5: 0cc970f0ec6bd236bf585ead276f62c2
Size: 1 MB
First Published: 2020-11-12 08:07:03 (5 years ago)
Latest Published: 2021-01-07 13:04:32 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-07 13:04:32 (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%\kaspersky lab
%windir%\temp\nagent_autopatches_960d8afb-60f9-4ee3-a8db-b9cdb6bef1c7_patch_12_0_0_7734_nagent_12_22020-11-23-08-40-10
%windir%\temp\nagent_autopatches_287aa144-0777-42ae-a0ff-11560274a422_patch_12_0_0_7734_nagent_12_22020-12-10-11-06-24

ThreatInfo has observed integrity_check_tool.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 8.1 33.3%
Windows Server 2012 R2 33.3%
Windows 7 33.3%

The most common operating system signal for integrity_check_tool.exe is Windows 8.1 with 33.3% 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.

integrity_check_tool.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 0x00106530
Image base 0x00400000

PE Sections:

Sections 6
Raw data 1771520

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

.text 1320960 bytes · 74.6% of section data
MD5 e3d1f434cb7f801f06bf95d6c773770a
.rdata 275968 bytes · 15.6% of section data
MD5 ba11cad3c9526ac9e9212e5a1ce47470
.data 95232 bytes · 5.4% of section data
MD5 8d89daf2cce4b8b3e01de80643f4934c
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 2048 bytes · 0.1% of section data
MD5 f9d50d329f86ce2d1187fb0c1786a0ee
.reloc 76800 bytes · 4.3% of section data
MD5 32575f44a04f6c7dc5e82d88d0acd26d

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 0cc970f0ec6bd236bf585ead276f62c2.
  • 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.