GridinSoft Threat Intelligence

chrome_elf.dll file report

Under review File reputation report
MD5 6e3eb158d65de17b66a9961b80bb7084
Latest seen 2025-11-18 23:00:43 (6 months ago)
First seen 2025-03-07 23:01:40 (a year ago)
Size 1 MB
Publisher OneStart.ai
Product OneStart
Signed by Apollo Technologies Inc

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-03-07 23:01:40 (a year ago); latest analysis 2025-11-18 23:00:43 (6 months ago).

Publisher context

Company metadata: OneStart.ai. Product metadata: OneStart.

Digital signature

Signed by Apollo Technologies Inc. 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 OneStart. The reported company name is OneStart.ai. The current detection status is Undefined, based on the latest analysis from 2025-11-18 23:00:43 (6 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: OneStart
Company Name: OneStart.ai
MD5: 6e3eb158d65de17b66a9961b80bb7084
Size: 1 MB
First Published: 2025-03-07 23:01:40 (a year ago)
Latest Published: 2025-11-18 23:00:43 (6 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-11-18 23:00:43 (6 months ago)

Overview

Signed By: Apollo Technologies Inc
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%\onestart.ai\onestart\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 United States
Share 100.0%
Low High activity

The strongest geographic signal for this file is United States 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 0x00092290
Image base 0x0000000180000000

PE Sections:

Sections 12
Raw data 1337856

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

.text 1027072 bytes · 76.8% of section data
MD5 7958b64593bf0a86555dfba68b17f0b4
.rdata 192512 bytes · 14.4% of section data
MD5 75c067701b774766146745a0736227d5
.data 61440 bytes · 4.6% of section data
MD5 6a732c9adffc23755560f71f382dea74
.pdata 34816 bytes · 2.6% of section data
MD5 86e9c0492f22e4145936625089c75a4a
.crthunk 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.gxfg 11264 bytes · 0.8% of section data
Uncommon name
MD5 6fd5bad0522f1799360ac070cf228bdf
.retplne 512 bytes · 0.0% of section data
Uncommon name
MD5 8c950f651287cbc1296bcb4e8cd7e990
.tls 512 bytes · 0.0% of section data
MD5 8b1935e51db1a9cad98313a9883b1db0
CPADinfo 512 bytes · 0.0% of section data
Uncommon name
MD5 60d3ea61d541c9be2e845d2787fb9574
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 fb34843965b65f09d7384b622b2a80eb
.rsrc 2048 bytes · 0.2% of section data
MD5 59731499f725a6c653d2a1c473e04816
.reloc 6144 bytes · 0.5% of section data
MD5 d64040b3e1b59316db5a9825aaa53a85

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 6e3eb158d65de17b66a9961b80bb7084.
  • 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.