GridinSoft Threat Intelligence

software_reporter_tool.exe file report

Clean record File reputation report
MD5 b4656e85333fed69fd85761fdce8b5d8
Latest seen 2022-09-05 23:04:03 (3 years ago)
First seen 2017-05-22 09:06:23 (9 years ago)
Size 1 MB
Publisher Google
Product Chrome Cleanup Tool
Signed by Google Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-22 09:06:23 (9 years ago); latest analysis 2022-09-05 23:04:03 (3 years ago).

Publisher context

Company metadata: Google. Product metadata: Chrome Cleanup Tool.

Digital signature

Signed by Google Inc. 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.

File context

software_reporter_tool.exe is a Windows file recorded in the ThreatInfo database. It is associated with Chrome Cleanup Tool. The reported company name is Google. The current detection status is Clean, based on the latest analysis from 2022-09-05 23:04:03 (3 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.

File Details

Product Name: Chrome Cleanup Tool
Company Name: Google
MD5: b4656e85333fed69fd85761fdce8b5d8
Size: 1 MB
First Published: 2017-05-22 09:06:23 (9 years ago)
Latest Published: 2022-09-05 23:04:03 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-09-05 23:04:03 (3 years ago)

Overview

Signed By: Google Inc
Status: Valid

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

Common Places:

%localappdata%\3810282d-6c19-47b0-8283-5c6c29a7e108\swreporter\5.39.1
%localappdata%\crxbro\user data\swreporter\5.39.1
%localappdata%\chroomium\user data\swreporter\5.39.1
%appdata%\hola\chromium_profile\swreporter\5.39.1
%localappdata%\guntony\user data\swreporter\5.39.1
%appdata%\extensions\swreporter\5.39.1
%localappdata%\cocesp\swreporter\5.39.1
%localappdata%\pecapale\swreporter\5.39.1
%localappdata%\arodeziraphvucerly\swreporter\5.39.1
%localappdata%\faciycilisykweied\swreporter\5.39.1

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

Geographic signal

Observed country distribution

ThreatInfo has seen software_reporter_tool.exe across 28 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Poland
Share 25.9%
Low High activity

The strongest geographic signal for this file is Poland with 25.9% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 56.1%
Windows 7 31.7%
Windows 8.1 9.1%
Windows 8 1.8%
Windows Vista 0.6%
Windows XP 0.6%

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

Analysis

software_reporter_tool.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 0x0006eaee
Image base 0x00400000

PE Sections:

Sections 6
Raw data 1476608

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

.text 573440 bytes · 38.8% of section data
MD5 9e4bb0be7d063c73693405f5a94fb70f
.rdata 449536 bytes · 30.4% of section data
MD5 073cd8f05354e62a1743db1ffac2a687
.data 24576 bytes · 1.7% of section data
MD5 e373af53ea55e06969fa67bb8b163501
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 392192 bytes · 26.6% of section data
MD5 7fa44f32d3b90d27079a702c2fbcd666
.reloc 36352 bytes · 2.5% of section data
MD5 a38a20450eae5c1da92380222ae969ff

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