GridinSoft Threat Intelligence
prefs.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.
First seen 2022-09-05 23:15:50 (3 years ago); latest analysis 2026-04-22 23:01:06 (a month ago).
Company metadata: Eclipse Adoptium. Product metadata: OpenJDK Platform 11.
Signed by Eclipse.org Foundation, Inc.. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
prefs.dll is a Windows file recorded in the ThreatInfo database. It is associated with OpenJDK Platform 11. The reported company name is Eclipse Adoptium. The current detection status is Undefined, based on the latest analysis from 2026-04-22 23:01:06 (a month ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.
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.
File Details
| Product Name: | OpenJDK Platform 11 |
| Company Name: | Eclipse Adoptium |
| MD5: | ff1402b3ebc596a3ad9e35c5a30aa62c |
| Size: | 23 KB |
| First Published: | 2022-09-05 23:15:50 (3 years ago) |
| Latest Published: | 2026-04-22 23:01:06 (a month ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2026-04-22 23:01:06 (a month ago) |
Overview
| Signed By: | Eclipse.org Foundation, Inc. |
| Status: | Valid |
The signature on prefs.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.
Common Places:
| %programfiles%\zona\jre |
ThreatInfo has observed prefs.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.
Geographic signal
Observed country distribution
ThreatInfo has seen prefs.dll across 14 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Russian Federation with 63.2% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for prefs.dll is Windows 10 with 97.1% 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.
Analysis
prefs.dll is identified as pe for 64-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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
0281115bfc92d7fbecb24ecadbce0af4
d7b062e096ad641c6540990633758d4c
bcdacb84b06b6d5de784487c9554a2c3
84f7bb87557b50e0ecf8811af0c1bd9d
cb898ae136b550cdba51dfb283331001
99bc1e703df5d6cc1096904397b5a646
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.