GridinSoft Threat Intelligence

mbedtls.dll file report

Under review File reputation report
MD5 99d353270cec8e49e9e380f28cd8165c
Latest seen 2025-04-12 23:01:56 (a year ago)
First seen 2025-04-12 23:01:45 (a year ago)
Size 363 KB
Publisher Arm
Product MbedTLS

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-04-12 23:01:45 (a year ago); latest analysis 2025-04-12 23:01:56 (a year ago).

Publisher context

Company metadata: Arm. Product metadata: MbedTLS.

Digital signature

Signed by BeiJing IQIYI Science & Techonology Co.,Ltd. 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.

mbedtls.dll is a Windows file recorded in the ThreatInfo database. It is associated with MbedTLS. The reported company name is Arm. The current detection status is Undefined, based on the latest analysis from 2025-04-12 23:01:56 (a year 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: MbedTLS
Company Name: Arm
MD5: 99d353270cec8e49e9e380f28cd8165c
Size: 363 KB
First Published: 2025-04-12 23:01:45 (a year ago)
Latest Published: 2025-04-12 23:01:56 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-04-12 23:01:56 (a year ago)

The signature on mbedtls.dll 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%\iqiyi video\lstyle\13.3.5.9162\qyappplugin

ThreatInfo has observed mbedtls.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 100.0%

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

mbedtls.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 0x0003f2b9
Image base 0x10000000

PE Sections:

Sections 5
Raw data 360448

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

.text 257536 bytes · 71.4% of section data
MD5 c5ccc8f3b8eab76c3a602f39154d95f3
.rdata 90624 bytes · 25.1% of section data
MD5 f04bdec5f35ba2766f2e434061753c29
.data 512 bytes · 0.1% of section data
MD5 e4e66c859eb05b3dd79d00761ef07fa8
.rsrc 1536 bytes · 0.4% of section data
MD5 edd45a4c8e81c753e9b7632ef166fdb7
.reloc 10240 bytes · 2.8% of section data
MD5 4b428b3819a310abd26d6489fe474e9d

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 99d353270cec8e49e9e380f28cd8165c.
  • 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.