GridinSoft Threat Intelligence

jvm.dll file report

Clean record File reputation report
MD5 24302f7ffcc90a17391e1ef2eee0bade
Latest seen 2025-09-18 23:00:38 (8 months ago)
First seen 2020-07-27 16:35:14 (5 years ago)
Size 3 MB
Publisher Oracle Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-07-27 16:35:14 (5 years ago); latest analysis 2025-09-18 23:00:38 (8 months ago).

Publisher context

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

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.

jvm.dll is a Windows file recorded in the ThreatInfo database. It is associated with Java(TM) Platform SE 8u212. The reported company name is Oracle Corporation. The current detection status is Clean, based on the latest analysis from 2025-09-18 23:00:38 (8 months 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 8u212
Company Name: Oracle Corporation
MD5: 24302f7ffcc90a17391e1ef2eee0bade
Size: 3 MB
First Published: 2020-07-27 16:35:14 (5 years ago)
Latest Published: 2025-09-18 23:00:38 (8 months ago)
Status: Clean (on last analysis)
Analysis Date: 2025-09-18 23:00:38 (8 months 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%\zona\jre\bin

ThreatInfo has observed jvm.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 77.7%
Windows 7 19.1%
Windows 8.1 3.2%

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

jvm.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 0x002c41d6
Image base 0x08000000

PE Sections:

Sections 5
Raw data 3885568

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

.text 2906624 bytes · 74.8% of section data
MD5 8a869c97b53413a619f2d8e13ad02017
.rdata 595968 bytes · 15.3% of section data
MD5 ba0eb1094d2c487fc0e5b31b68a094cd
.data 142336 bytes · 3.7% of section data
MD5 4faf4c8ed98879476add535ed7469433
.rsrc 1536 bytes · 0.0% of section data
MD5 0b3f76c080254f06b241e9c6d7ef6487
.reloc 239104 bytes · 6.2% of section data
MD5 9d02d2785c79557ab6911bdb4e3cc83a

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 24302f7ffcc90a17391e1ef2eee0bade.
  • 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.