GridinSoft Threat Intelligence

libwinpthread-1.dll file report

Under review File reputation report
MD5 1aca06d325b44ca427ea37b28a0497b5
Latest seen 2021-11-23 21:47:47 (4 years ago)
First seen 2018-01-21 00:05:49 (8 years ago)
Size 290 KB
Publisher MingW-W64 Project. All rights reserved.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-01-21 00:05:49 (8 years ago); latest analysis 2021-11-23 21:47:47 (4 years ago).

Publisher context

Company metadata: MingW-W64 Project. All rights reserved..

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

File context

libwinpthread-1.dll is a Windows file recorded in the ThreatInfo database. The reported company name is MingW-W64 Project. All rights reserved.. The current detection status is Undefined, based on the latest analysis from 2021-11-23 21:47:47 (4 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.

File Details

Company Name: MingW-W64 Project. All rights reserved.
MD5: 1aca06d325b44ca427ea37b28a0497b5
Size: 290 KB
First Published: 2018-01-21 00:05:49 (8 years ago)
Latest Published: 2021-11-23 21:47:47 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-11-23 21:47:47 (4 years ago)

Common Places:

%commonappdata%
%sysdrive%
%commonappdata%\windows
%startup%
%sysdrive%\miner\1906\bin

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

File Names:

2 observed names
libwinpthread-1.dll libwinpthread-1.dll.quarantined

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Geographic signal

Observed country distribution

ThreatInfo has seen libwinpthread-1.dll across 27 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Taiwan
Share 85.4%
Low High activity

The strongest geographic signal for this file is Taiwan with 85.4% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 7 62.0%
Windows 10 35.1%
Windows 8.1 2.8%

The most common operating system signal for libwinpthread-1.dll is Windows 7 with 62.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.

Analysis

libwinpthread-1.dll is identified as pe for 64-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 64-bit
Subsystem Windows CUI
Entry point 0x000013e0
Image base 0x0000000064940000

PE Sections:

Sections 20
Raw data 248320

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

.text 31232 bytes · 12.6% of section data
MD5 95e0d6d6a9282a7d8c6c604f07ff4204
.data 512 bytes · 0.2% of section data
MD5 23588f13706ef05cbb1f1e44115dc771
.rdata 2560 bytes · 1.0% of section data
MD5 f2d93de92c72a16ade6131a0c3c32509
.pdata 3072 bytes · 1.2% of section data
MD5 b83d5a85731bbfb9225a7247567825f0
.xdata 2560 bytes · 1.0% of section data
Uncommon name
MD5 e2e2d9952fbd0031326db2789b669d35
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 4608 bytes · 1.9% of section data
MD5 7660fa89eec8930b935365b0d68a1e64
.idata 3584 bytes · 1.4% of section data
MD5 cb0da96e31ac86eb1269fe5467f74e1b
.CRT 512 bytes · 0.2% of section data
MD5 88c10636c459c61369abacd987977511
.tls 512 bytes · 0.2% of section data
MD5 f5b36413dada8c962f29e7d8cbed9287
.rsrc 1536 bytes · 0.6% of section data
MD5 4ca3d1f69c391b07e41e71081a55220f
.reloc 512 bytes · 0.2% of section data
MD5 7b6b0988ae0681603640de9cf5de5e8a
/4 1536 bytes · 0.6% of section data
Uncommon name
MD5 a3493203ccd1d655037f74aba682de60
/19 89088 bytes · 35.9% of section data
Uncommon name
MD5 d4a7677500a0ca1a9246315939f3bc91
/31 13312 bytes · 5.4% of section data
Uncommon name
MD5 4019a045e869881117a0cfbd20af3985
/45 16896 bytes · 6.8% of section data
Uncommon name
MD5 78b1ef1b8e6c0841199e9d7247d47573
/57 12800 bytes · 5.2% of section data
Uncommon name
MD5 7fb0b8edc624bfa857643147abd02554
/70 2560 bytes · 1.0% of section data
Uncommon name
MD5 aae79ad1cc6d5bf09b69077fc23cdfed
/81 56320 bytes · 22.7% of section data
Uncommon name
MD5 bd4f5bfdb1b3a97558a6702b3535de36
/92 4608 bytes · 1.9% of section data
Uncommon name
MD5 7e591eacabc215186366188d55049194

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 1aca06d325b44ca427ea37b28a0497b5.
  • 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.