GridinSoft Threat Intelligence

putsig.dll file report

Clean record File reputation report
MD5 55aa0c8e45f0abd7f2c613cd4bc10361
Latest seen 2024-01-06 23:20:00 (2 years ago)
First seen 2024-01-06 23:20:00 (2 years ago)
Size 82 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-01-06 23:20:00 (2 years ago); latest analysis 2024-01-06 23:20:00 (2 years ago).

Publisher context

Company metadata: Panda Security, S.L.. Product metadata: Panda Utilities System.

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.

putsig.dll is a Windows file recorded in the ThreatInfo database. It is associated with Panda Utilities System. 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:20:00 (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 Utilities System
Company Name: Panda Security, S.L.
MD5: 55aa0c8e45f0abd7f2c613cd4bc10361
Size: 82 KB
First Published: 2024-01-06 23:20:00 (2 years ago)
Latest Published: 2024-01-06 23:20:00 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-01-06 23:20:00 (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 putsig.dll 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 putsig.dll 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.

putsig.dll 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 0x00003b7e
Image base 0x10000000

PE Sections:

Sections 5
Raw data 69120

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

.text 48640 bytes · 70.4% of section data
MD5 4189a01dc93729522a1455fcdb95b60d
.rdata 11264 bytes · 16.3% of section data
MD5 c7f6e65811d28720592806f1cf0cdcb6
.data 4096 bytes · 5.9% of section data
MD5 9bfcc1bb791d07574a930465e1302f38
.rsrc 1536 bytes · 2.2% of section data
MD5 998431ecd22944b71b0baa671dec3756
.reloc 3584 bytes · 5.2% of section data
MD5 7676e52659fb96d8ca7b5bb63401b4f8

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 55aa0c8e45f0abd7f2c613cd4bc10361.
  • 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.