GridinSoft Threat Intelligence

Jade.dll file report

Under review File reputation report
MD5 10265d0a23dc19c2dbbc0d058af6c8eb
Latest seen 2025-06-30 23:00:33 (11 months ago)
First seen 2025-06-30 23:00:33 (11 months ago)
Size 2 MB
Product Jade.dll

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-06-30 23:00:33 (11 months ago); latest analysis 2025-06-30 23:00:33 (11 months ago).

Publisher context

Company metadata: 北京小树发芽网络科技有限公司. Product metadata: Jade.dll.

Digital signature

Signed by Beijing Xiaoshu Germination Network 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.

Jade.dll is a Windows file recorded in the ThreatInfo database. It is associated with Jade.dll. The reported company name is 北京小树发芽网络科技有限公司. The current detection status is Undefined, based on the latest analysis from 2025-06-30 23:00:33 (11 months 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: Jade.dll
Company Name: 北京小树发芽网络科技有限公司
MD5: 10265d0a23dc19c2dbbc0d058af6c8eb
Size: 2 MB
First Published: 2025-06-30 23:00:33 (11 months ago)
Latest Published: 2025-06-30 23:00:33 (11 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-06-30 23:00:33 (11 months ago)

The signature on Jade.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.

%localappdata%

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

Jade.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 0x00026410
Image base 0x10000000

PE Sections:

Sections 5
Raw data 2204672

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

.text 1586176 bytes · 71.9% of section data
MD5 954d9363314b78c75e1bfd1c5ddd4670
.rdata 488960 bytes · 22.2% of section data
MD5 ef9d1300ab6d9728badb533aeb9e28e7
.data 43008 bytes · 2.0% of section data
MD5 718925ae2108fc06c2b42af674002de6
.rsrc 8192 bytes · 0.4% of section data
MD5 d6251093791ae03adf35c45b92fa357f
.reloc 78336 bytes · 3.6% of section data
MD5 6ec48336f30af51bbb0161a00804fc44

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 10265d0a23dc19c2dbbc0d058af6c8eb.
  • 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.