GridinSoft Threat Intelligence
tbaseregistry32.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2018-04-11 22:10:17 (8 years ago); latest analysis 2024-08-14 23:01:47 (2 years ago).
Company metadata: Advanced Micro Devices, Inc. . Product metadata: Advanced Micro Devices, Inc. tbaseregistry dll.
Signed by Microsoft Windows Hardware Compatibility Publisher. ThreatInfo marks this publisher as trusted for this record.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
tbaseregistry32.dll is a Windows file recorded in the ThreatInfo database. It is associated with Advanced Micro Devices, Inc. tbaseregistry dll. The reported company name is Advanced Micro Devices, Inc. . The current detection status is Clean, based on the latest analysis from 2024-08-14 23:01:47 (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.
File Details
| Product Name: | Advanced Micro Devices, Inc. tbaseregistry dll |
| Company Name: | Advanced Micro Devices, Inc. |
| MD5: | 252057d248c48f2a97a142a9f919b9ff |
| Size: | 105 KB |
| First Published: | 2018-04-11 22:10:17 (8 years ago) |
| Latest Published: | 2024-08-14 23:01:47 (2 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2024-08-14 23:01:47 (2 years ago) |
Overview
| Signed By: | Microsoft Windows Hardware Compatibility Publisher |
| 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.
Common Places:
| %programfiles%\drivertoolkit\download\b2c338548bcc27d624f21a6ef35de0a1\radeon-software-crimson-relive-17.30-09aug\packages\drivers\amdpsp |
| %localappdata%\slimware utilities inc\driverupdate\backups\20190406t001110407800\pci |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20200425t221221835983\pci |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20200425t225635658786\pci |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20200425t211410161704\pci |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20180122t201154419030\pci |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20200203t153948297194\pci |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20180807t002156455154\pci |
ThreatInfo has observed tbaseregistry32.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.
Geographic signal
Observed country distribution
ThreatInfo has seen tbaseregistry32.dll across 11 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Argentina with 18.8% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for tbaseregistry32.dll is Windows 10 with 68.8% 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
tbaseregistry32.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
91ff8a132da7ab8b7a1a778ef7a726d6
2ee79052ff7a3e379eee94fc29b42fef
eca0ae53c322ecc77d600b15f7e62a84
c30541504bd7de9d5fd8ffe6db0b8123
1065ef4da4d048697339f42d5b2f18fa
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.