GridinSoft Threat Intelligence

jvm.dll file report

Clean record File reputation report
MD5 21476ea0e22a9764eaf7ffba84b9b578
Latest seen 2021-02-03 04:49:15 (5 years ago)
First seen 2021-02-03 04:49:15 (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 2021-02-03 04:49:15 (5 years ago); latest analysis 2021-02-03 04:49:15 (5 years ago).

Publisher context

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

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 8u162. The reported company name is Oracle Corporation. The current detection status is Clean, based on the latest analysis from 2021-02-03 04:49:15 (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 8u162
Company Name: Oracle Corporation
MD5: 21476ea0e22a9764eaf7ffba84b9b578
Size: 3 MB
First Published: 2021-02-03 04:49:15 (5 years ago)
Latest Published: 2021-02-03 04:49:15 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-03 04:49:15 (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%\bootmod3\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 100.0%

The most common operating system signal for jvm.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.

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 0x002c12d6
Image base 0x6d160000

PE Sections:

Sections 5
Raw data 3866112

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

.text 2894848 bytes · 74.9% of section data
MD5 25c2281dd11eba23b81b1377b5a6d697
.rdata 590336 bytes · 15.3% of section data
MD5 c41835737cd6e47d184d8bfe810dd188
.data 141824 bytes · 3.7% of section data
MD5 a4a330930f0a0d30019d189db6a53f56
.rsrc 1536 bytes · 0.0% of section data
MD5 1351b81ab86279cc85a2696b21e9d97d
.reloc 237568 bytes · 6.1% of section data
MD5 1d8bc0f5bf420f9e05559b701512c22a

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 21476ea0e22a9764eaf7ffba84b9b578.
  • 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.