GridinSoft Threat Intelligence

AdbSdk.dll file report

Under review File reputation report
MD5 76b3979cfb767b27f5e1528270b647e0
Latest seen 2021-09-11 20:36:31 (4 years ago)
First seen 2021-09-11 20:36:31 (4 years ago)
Size 209 KB
Publisher Tenorshare
Product Android ADB API

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-09-11 20:36:31 (4 years ago); latest analysis 2021-09-11 20:36:31 (4 years ago).

Publisher context

Company metadata: Tenorshare. Product metadata: Android ADB API.

Digital signature

Signed by Tenorshare 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.

AdbSdk.dll is a Windows file recorded in the ThreatInfo database. It is associated with Android ADB API. The reported company name is Tenorshare. The current detection status is Undefined, based on the latest analysis from 2021-09-11 20:36:31 (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.

Product Name: Android ADB API
Company Name: Tenorshare
MD5: 76b3979cfb767b27f5e1528270b647e0
Size: 209 KB
First Published: 2021-09-11 20:36:31 (4 years ago)
Latest Published: 2021-09-11 20:36:31 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-09-11 20:36:31 (4 years ago)
Signed By: Tenorshare Co., Ltd.
Status: Valid

The signature on AdbSdk.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%\tenorshare

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

AdbSdk.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 0x000248f0
Image base 0x10000000

PE Sections:

Sections 5
Raw data 197632

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

.text 156672 bytes · 79.3% of section data
MD5 4553e957519bf6340e2f1fcd3d90b1a1
.rdata 29696 bytes · 15.0% of section data
MD5 c121d485819c3f05041cf72c430583ce
.data 2048 bytes · 1.0% of section data
MD5 8cfe7b761f4d8874d28fc8d38e21323a
.rsrc 1536 bytes · 0.8% of section data
MD5 58442532eb1491804baad64e7e5454f0
.reloc 7680 bytes · 3.9% of section data
MD5 734a1cd9b16b64e39a5bc85e4d2fe751

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 76b3979cfb767b27f5e1528270b647e0.
  • 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.