GridinSoft Threat Intelligence

bspatch.exe file report

Clean record File reputation report
MD5 b58a76c6829fae128a10de88e99499e4
Latest seen 2024-01-06 23:13:58 (2 years ago)
First seen 2020-09-10 19:29:35 (5 years ago)
Size 77 KB
Product Panda Utility
Signed by Panda Security S.L

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-09-10 19:29:35 (5 years ago); latest analysis 2024-01-06 23:13:58 (2 years ago).

Publisher context

Company metadata: Panda Security, S.L.. Product metadata: Panda Utility.

Digital signature

Signed by Panda Security S.L. 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.

bspatch.exe is a Windows file recorded in the ThreatInfo database. It is associated with Panda Utility. The reported company name is Panda Security, S.L.. The current detection status is Clean, based on the latest analysis from 2024-01-06 23:13:58 (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: Panda Utility
Company Name: Panda Security, S.L.
MD5: b58a76c6829fae128a10de88e99499e4
Size: 77 KB
First Published: 2020-09-10 19:29:35 (5 years ago)
Latest Published: 2024-01-06 23:13:58 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-01-06 23:13:58 (2 years ago)
Signed By: Panda Security S.L
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%\telmex

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

bspatch.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 0x000059f2
Image base 0x00400000

PE Sections:

Sections 4
Raw data 69632

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

.text 49152 bytes · 70.6% of section data
MD5 090067597a74db606d46dace7816c5d6
.rdata 8192 bytes · 11.8% of section data
MD5 9fa0d3c56085b5cbc9e4c5061235f123
.data 8192 bytes · 11.8% of section data
MD5 f472bc131c7dfedab69c3abda663f910
.rsrc 4096 bytes · 5.9% of section data
MD5 84aa5fabc679345382a7dcb997bf5056

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