GridinSoft Threat Intelligence

jli.dll file report

Clean record File reputation report
MD5 b2a9bfe73329ebd4bdb463d3857db6d6
Latest seen 2021-04-14 20:51:07 (5 years ago)
First seen 2018-11-13 12:07:56 (7 years ago)
Size 139 KB
Publisher Oracle Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-11-13 12:07:56 (7 years ago); latest analysis 2021-04-14 20:51:07 (5 years ago).

Publisher context

Company metadata: Oracle Corporation. Product metadata: Java(TM) Platform SE 7 U45.

Digital signature

Signed by Oracle America, Inc.. 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.

jli.dll is a Windows file recorded in the ThreatInfo database. It is associated with Java(TM) Platform SE 7 U45. The reported company name is Oracle Corporation. The current detection status is Clean, based on the latest analysis from 2021-04-14 20:51:07 (5 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: Java(TM) Platform SE 7 U45
Company Name: Oracle Corporation
MD5: b2a9bfe73329ebd4bdb463d3857db6d6
Size: 139 KB
First Published: 2018-11-13 12:07:56 (7 years ago)
Latest Published: 2021-04-14 20:51:07 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-04-14 20:51:07 (5 years ago)
Signed By: Oracle America, Inc.
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%\falcon\falcon box\data\x10flasher_lib\winjre32
%programfiles%\uni-android tool 7.0 by technical computer solutions\unifiles\x10flasher_lib\winjre32

ThreatInfo has observed jli.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 50.0%
Windows 10 50.0%

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

jli.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 0x0000c267
Image base 0x6e160000

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 93696 bytes · 69.3% of section data
MD5 ee942e214d27e03e2857b8a62b7147eb
.rdata 29696 bytes · 22.0% of section data
MD5 3cfd95083f69f9ba7fd7b9861f224826
.data 4608 bytes · 3.4% of section data
MD5 145ecc8037b289d919c8e2936b7bedea
.rsrc 1024 bytes · 0.8% of section data
MD5 2b0b8703a7a190368874e81bff85289f
.reloc 6144 bytes · 4.5% of section data
MD5 ec2e5b0be1935cd915a24b821bd6ec92

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