GridinSoft Threat Intelligence
chrome_elf.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2024-09-04 23:01:46 (2 years ago); latest analysis 2025-07-17 23:01:00 (10 months ago).
Company metadata: Adaptive Bee. Product metadata: UR.
Signed by AdaptiveBee SAS. 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
chrome_elf.dll is a Windows file recorded in the ThreatInfo database. It is associated with UR. The reported company name is Adaptive Bee. The current detection status is Undefined, based on the latest analysis from 2025-07-17 23:01:00 (10 months ago).
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: | UR |
| Company Name: | Adaptive Bee |
| MD5: | cb8f89c7c2fb18950ce95c995d12eb30 |
| Size: | 1 MB |
| First Published: | 2024-09-04 23:01:46 (2 years ago) |
| Latest Published: | 2025-07-17 23:01:00 (10 months ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2025-07-17 23:01:00 (10 months ago) |
Overview
| Signed By: | AdaptiveBee SAS |
| Status: | Valid |
The signature on chrome_elf.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:
| %localappdata%\urbrowser\application |
ThreatInfo has observed chrome_elf.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 chrome_elf.dll across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Egypt with 33.3% 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 chrome_elf.dll is Windows 10 with 66.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.
Analysis
chrome_elf.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.
94f3ccf5b8bd726554cf10d5944634ba
ca615aae8bace7a39be9c0be21815a90
e36df8dd7b2f07c2187fc2273e2da7cb
90e40140c815162a0cd3ea527465046c
2f51fbe2188123421ee0209618945543
bf619eac0cdf3f68d496ea9344137e8b
062eeb7b80b761be355d335d4403fcca
bf619eac0cdf3f68d496ea9344137e8b
8ba86516d84cef220ecd4ff8550b6df0
1f354d76203061bfdd5a53dae48d5435
60d3ea61d541c9be2e845d2787fb9574
1e519e144ec0c5dd9615beb4771e3c4f
ee3a6cd2780991e13b551b38c28cfbb6
07b9543015fee54d3f0b522fc3811875
48f1e77ab62ab4a5e16865f9184f3b81
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.