GridinSoft Threat Intelligence

LDSBasic.dll file report

Under review File reputation report
MD5 b8da66f1d207c1048e3fe69464830eef
Latest seen 2024-09-08 23:01:11 (2 years ago)
First seen 2019-05-24 14:27:46 (7 years ago)
Size 1 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-05-24 14:27:46 (7 years ago); latest analysis 2024-09-08 23:01:11 (2 years ago).

Publisher context

Product metadata: 鲁大师基础功能模块.

Digital signature

Signed by Beijing Qihu Technology 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.

LDSBasic.dll is a Windows file recorded in the ThreatInfo database. It is associated with 鲁大师基础功能模块. The current detection status is Undefined, based on the latest analysis from 2024-09-08 23:01:11 (2 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: 鲁大师基础功能模块
MD5: b8da66f1d207c1048e3fe69464830eef
Size: 1 MB
First Published: 2019-05-24 14:27:46 (7 years ago)
Latest Published: 2024-09-08 23:01:11 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-09-08 23:01:11 (2 years ago)
Signed By: Beijing Qihu Technology Co., Ltd.
Status: Valid

The signature on LDSBasic.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%\ldslite
%programfiles%\ludashi
%appdata%\360bizhi

ThreatInfo has observed LDSBasic.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 90.2%
Windows 7 7.8%
Windows 8.1 2.0%

The most common operating system signal for LDSBasic.dll is Windows 10 with 90.2% 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.

LDSBasic.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 0x00059790
Image base 0x10000000

PE Sections:

Sections 5
Raw data 1728000

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

.text 1412096 bytes · 81.7% of section data
MD5 d9acd8895b330a3bd6e489099f1fd888
.rdata 223744 bytes · 12.9% of section data
MD5 a960aa19ca7e2bc44d1442b1a59a4f84
.data 38400 bytes · 2.2% of section data
MD5 01c2be9bcbbe38530bf1dc5228443265
.rsrc 1536 bytes · 0.1% of section data
MD5 94cadab642f1cfc247cdfabde0484949
.reloc 52224 bytes · 3.0% of section data
MD5 de2c4ce5bbb9a659ad3b0f5c2e6d8519

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