GridinSoft Threat Intelligence

NdkApi.Communication.dll file report

Clean record File reputation report
MD5 08a533dc2a8538b822e46b8c7c3b563e
Latest seen 2024-01-06 23:20:51 (2 years ago)
First seen 2021-07-26 20:39:21 (4 years ago)
Size 148 KB
Product Consumer NDK

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-07-26 20:39:21 (4 years ago); latest analysis 2024-01-06 23:20:51 (2 years ago).

Publisher context

Company metadata: Panda Security, S.L.. Product metadata: Consumer NDK.

Digital signature

Signed by Panda Security S.L.. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

NdkApi.Communication.dll is a Windows file recorded in the ThreatInfo database. It is associated with Consumer NDK. The reported company name is Panda Security, S.L.. The current detection status is Clean, based on the latest analysis from 2024-01-06 23:20:51 (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.

Product Name: Consumer NDK
Company Name: Panda Security, S.L.
MD5: 08a533dc2a8538b822e46b8c7c3b563e
Size: 148 KB
First Published: 2021-07-26 20:39:21 (4 years ago)
Latest Published: 2024-01-06 23:20:51 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-01-06 23:20:51 (2 years ago)
Signed By: Panda Security S.L.
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.

%programfiles%\telmex

ThreatInfo has observed NdkApi.Communication.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 10 100.0%

The most common operating system signal for NdkApi.Communication.dll is Windows 10 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.

NdkApi.Communication.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 0x00013b90
Image base 0x10000000

PE Sections:

Sections 5
Raw data 135168

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

.text 85504 bytes · 63.3% of section data
MD5 f4f5b73435d9dab7a59e90ebd4f2a2a9
.rdata 27648 bytes · 20.5% of section data
MD5 c3d639bf740c5c780520beb63c0ac558
.data 7680 bytes · 5.7% of section data
MD5 97a85c88a945264209dc46417bf1869d
.rsrc 1536 bytes · 1.1% of section data
MD5 db6d54cca2997b9f260e2e5181b44279
.reloc 12800 bytes · 9.5% of section data
MD5 45a884d21e2fab1a4babe405c647cb6d

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.

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 08a533dc2a8538b822e46b8c7c3b563e.
  • 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.