GridinSoft Threat Intelligence

ptusredt.dll file report

Clean record File reputation report
MD5 de9e54b824365c05941b2edaf5a37882
Latest seen 2024-04-29 23:02:33 (2 years ago)
First seen 2024-01-25 23:59:46 (2 years ago)
Size 165 KB
Publisher Cisco WebEx LLC
Product WebEx One-Click
Signed by Cisco WebEx LLC

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-01-25 23:59:46 (2 years ago); latest analysis 2024-04-29 23:02:33 (2 years ago).

Publisher context

Company metadata: Cisco WebEx LLC. Product metadata: WebEx One-Click.

Digital signature

Signed by Cisco WebEx LLC. 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.

ptusredt.dll is a Windows file recorded in the ThreatInfo database. It is associated with WebEx One-Click. The reported company name is Cisco WebEx LLC. The current detection status is Clean, based on the latest analysis from 2024-04-29 23:02:33 (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: WebEx One-Click
Company Name: Cisco WebEx LLC
MD5: de9e54b824365c05941b2edaf5a37882
Size: 165 KB
First Published: 2024-01-25 23:59:46 (2 years ago)
Latest Published: 2024-04-29 23:02:33 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-04-29 23:02:33 (2 years ago)
Signed By: Cisco WebEx LLC
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.

%desktop%
%profile%\downloads

ThreatInfo has observed ptusredt.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 50.0%
Windows 7 50.0%

The most common operating system signal for ptusredt.dll is Windows 10 with 50.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.

ptusredt.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 0x000070f5
Image base 0x10000000

PE Sections:

Sections 5
Raw data 153600

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

.text 95232 bytes · 62.0% of section data
MD5 38cdf26e3188a077965627433e0b0e9d
.rdata 43008 bytes · 28.0% of section data
MD5 442d5243bcff59b00efcf801ff55e566
.data 3584 bytes · 2.3% of section data
MD5 6d144daf2b2be8efb1380aa86e23abd4
.rsrc 5120 bytes · 3.3% of section data
MD5 557e60b21be90d808d059551882d6bba
.reloc 6656 bytes · 4.3% of section data
MD5 c3d094ba9290fe766da09342cbe9cc8b

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