GridinSoft Threat Intelligence

pthreadVC2.dll file report

Under review File reputation report
MD5 0ab7d0e87f3843f8104b3670f5a9af62
Latest seen 2024-05-15 23:01:22 (2 years ago)
First seen 2017-05-21 03:01:53 (9 years ago)
Size 84 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 03:01:53 (9 years ago); latest analysis 2024-05-15 23:01:22 (2 years ago).

Publisher context

Company metadata: Open Source Software community project.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

pthreadVC2.dll is a Windows file recorded in the ThreatInfo database. The reported company name is Open Source Software community project. The current detection status is Undefined, based on the latest analysis from 2024-05-15 23:01:22 (2 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Company Name: Open Source Software community project
MD5: 0ab7d0e87f3843f8104b3670f5a9af62
Size: 84 KB
First Published: 2017-05-21 03:01:53 (9 years ago)
Latest Published: 2024-05-15 23:01:22 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-05-15 23:01:22 (2 years ago)
%programfiles%\pandora.tv\panservice
%localappdata%\playfree browser\games\best_spider_solitaire-gs_gmigp\data\win32dll
%programfiles%\pandora.tv
%localappdata%\playfree browser\games\best_spider_solitaire-gs_gi\data
%commonappdata%
%programfiles%
%programfiles%\orange\ma livebox

ThreatInfo has observed pthreadVC2.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 7 60.6%
Windows 10 14.9%
Windows XP 11.0%
Windows 8.1 9.8%
Windows 8 3.6%
Windows Vista 0.2%

The most common operating system signal for pthreadVC2.dll is Windows 7 with 60.6% 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.

pthreadVC2.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 0x0000d0fd
Image base 0x10000000

PE Sections:

Sections 6
Raw data 81920

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

.text 57344 bytes · 70.0% of section data
MD5 141ad2be6d77b003f10f008501d26e72
.rdata 8192 bytes · 10.0% of section data
MD5 5121c98b2a11dcfb32f4d8c5fd744250
.data 4096 bytes · 5.0% of section data
MD5 15d6b38e54707087d081dfb8702a49ee
.idata 4096 bytes · 5.0% of section data
MD5 66a74830acfca8adf3717f3973242db3
.rsrc 4096 bytes · 5.0% of section data
MD5 8126b5a677df33121d85968c3b59d6cd
.reloc 4096 bytes · 5.0% of section data
MD5 8704034086e429c1edf1eef17e06a403

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 0ab7d0e87f3843f8104b3670f5a9af62.
  • 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.