GridinSoft Threat Intelligence

LIBCURL.EXE file report

Under review File reputation report
MD5 b5dd0c09d25aa8e2f0445472406c4d1c
Latest seen 2022-11-12 23:16:13 (3 years ago)
First seen 2021-01-08 06:16:41 (5 years ago)
Size 378 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-08 06:16:41 (5 years ago); latest analysis 2022-11-12 23:16:13 (3 years ago).

Publisher context

Company metadata: curl, https://curl.haxx.se/. Product metadata: The curl executable.

Digital signature

Signed by Tencent Technology(Shenzhen) Company Limited. The signature is reported as valid, but signed files can still be bundled or abused.

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.

LIBCURL.EXE is a Windows file recorded in the ThreatInfo database. It is associated with The curl executable. The reported company name is curl, https://curl.haxx.se/. The current detection status is Undefined, based on the latest analysis from 2022-11-12 23:16:13 (3 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.

Product Name: The curl executable
Company Name: curl, https://curl.haxx.se/
MD5: b5dd0c09d25aa8e2f0445472406c4d1c
Size: 378 KB
First Published: 2021-01-08 06:16:41 (5 years ago)
Latest Published: 2022-11-12 23:16:13 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-11-12 23:16:13 (3 years ago)

The signature on LIBCURL.EXE is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%programfiles%\tencent

ThreatInfo has observed LIBCURL.EXE 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 63.6%
Windows 10 27.3%
Windows 8.1 9.1%

The most common operating system signal for LIBCURL.EXE is Windows 7 with 63.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.

LIBCURL.EXE is identified as pe for 32-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 32-bit
Subsystem Windows CUI
Entry point 0x00012366
Image base 0x00400000

PE Sections:

Sections 4
Raw data 368640

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

.text 118784 bytes · 32.2% of section data
MD5 cb2b67ccf6983b2b36f25f056f7c320a
.rdata 225280 bytes · 61.1% of section data
MD5 c82f4a2417e1393e2d7845391c18457b
.data 4096 bytes · 1.1% of section data
MD5 1ee7c2e86a728f2d8c6fa1a7ddfa9a73
.rsrc 20480 bytes · 5.6% of section data
MD5 48c4a6bcf2beff012b6c3b6656d6776f

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