GridinSoft Threat Intelligence

chrome_elf.dll file report

Under review File reputation report
MD5 11af73b68f7cca69db1859e4cacc57db
Latest seen 2024-08-23 23:08:19 (2 years ago)
First seen 2024-08-23 23:08:19 (2 years ago)
Size 1 MB
Publisher Adaptive Bee
Product UR
Signed by AdaptiveBee SAS

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-08-23 23:08:19 (2 years ago); latest analysis 2024-08-23 23:08:19 (2 years ago).

Publisher context

Company metadata: Adaptive Bee. Product metadata: UR.

Digital signature

Signed by AdaptiveBee SAS. The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. 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 2024-08-23 23:08:19 (2 years 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: 11af73b68f7cca69db1859e4cacc57db
Size: 1 MB
First Published: 2024-08-23 23:08:19 (2 years ago)
Latest Published: 2024-08-23 23:08:19 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-23 23:08:19 (2 years 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 1 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Mexico
Share 100.0%
Low High activity

The strongest geographic signal for this file is Mexico with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 100.0%

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

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.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x0007de50
Image base 0x0000000180000000

PE Sections:

Sections 14
Raw data 1249280

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

.text 966656 bytes · 77.4% of section data
MD5 f48d2cf8ba2f296b3bc23b3599c2d861
.rdata 158720 bytes · 12.7% of section data
MD5 d506424c619ca6d2a6d52e6e867f3b89
.data 64512 bytes · 5.2% of section data
MD5 7e1063a0acd4a9f8baaf77518471431f
.pdata 35840 bytes · 2.9% of section data
MD5 81703e47399cbce7219b8172a0b7e85e
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 d6274d7c7ce8ac1ad63e4af1e1f0e8e9
.crthunk 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.gxfg 11776 bytes · 0.9% of section data
Uncommon name
MD5 062eeb7b80b761be355d335d4403fcca
.oldntma 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.retplne 512 bytes · 0.0% of section data
Uncommon name
MD5 8ba86516d84cef220ecd4ff8550b6df0
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
CPADinfo 512 bytes · 0.0% of section data
Uncommon name
MD5 60d3ea61d541c9be2e845d2787fb9574
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 971c350d99327615480d374e714b6996
.rsrc 2048 bytes · 0.2% of section data
MD5 2e665b4686ffc3fdfe76efc2a2b1caeb
.reloc 6144 bytes · 0.5% of section data
MD5 dda5c3647cb7d6bc8e55c7a5f89deb9e

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.

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 11af73b68f7cca69db1859e4cacc57db.
  • 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.