GridinSoft Threat Intelligence

jp2ssv.dll file report

Clean record File reputation report
MD5 f78ca16c5550c0283403dd3147422044
Latest seen 2024-04-29 23:02:25 (2 years ago)
First seen 2024-04-29 23:02:25 (2 years ago)
Size 169 KB
Publisher Oracle Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-04-29 23:02:25 (2 years ago); latest analysis 2024-04-29 23:02:25 (2 years ago).

Publisher context

Company metadata: Oracle Corporation. Product metadata: Java(TM) Platform SE 8 U91.

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.

jp2ssv.dll is a Windows file recorded in the ThreatInfo database. It is associated with Java(TM) Platform SE 8 U91. The reported company name is Oracle Corporation. The current detection status is Clean, based on the latest analysis from 2024-04-29 23:02:25 (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: Java(TM) Platform SE 8 U91
Company Name: Oracle Corporation
MD5: f78ca16c5550c0283403dd3147422044
Size: 169 KB
First Published: 2024-04-29 23:02:25 (2 years ago)
Latest Published: 2024-04-29 23:02:25 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-04-29 23:02:25 (2 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.

%sysdrive%\tat dental crdh\data\jre_x86

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

jp2ssv.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 0x0000dd6b
Image base 0x6fd10000

PE Sections:

Sections 5
Raw data 165888

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

.text 121856 bytes · 73.5% of section data
MD5 1e3f1c8c409a4a10e5891b18d665d2f0
.rdata 26112 bytes · 15.7% of section data
MD5 610d8684f59c6ec0c90936b0d46694a8
.data 5632 bytes · 3.4% of section data
MD5 5f655ff68e69222b16bf6ad13b82e843
.rsrc 3072 bytes · 1.9% of section data
MD5 2986e322af663ff3a907fc9148ed9eb7
.reloc 9216 bytes · 5.6% of section data
MD5 5e4620a12b93fbc986fbbd1f3cc29582

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