GridinSoft Threat Intelligence

chrome_elf.dll file report

Under review File reputation report
MD5 24f7377d2c472dbf0bd8ff9d6bcfb1a4
Latest seen 2024-01-03 23:19:31 (2 years ago)
First seen 2024-01-03 23:19:31 (2 years ago)
Size 132 KB
Product Orbitum
Signed by Bergarius Limited

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

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

Publisher context

Company metadata: The Orbitum Authors. Product metadata: Orbitum.

Digital signature

Signed by Bergarius Limited. 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.

chrome_elf.dll is a Windows file recorded in the ThreatInfo database. It is associated with Orbitum. The reported company name is The Orbitum Authors. The current detection status is Undefined, based on the latest analysis from 2024-01-03 23:19:31 (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.

Product Name: Orbitum
Company Name: The Orbitum Authors
MD5: 24f7377d2c472dbf0bd8ff9d6bcfb1a4
Size: 132 KB
First Published: 2024-01-03 23:19:31 (2 years ago)
Latest Published: 2024-01-03 23:19:31 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-03 23:19:31 (2 years ago)
Signed By: Bergarius Limited
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.

%localappdata%\orbitum\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.

chrome_elf.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 0x00008226
Image base 0x01c20000

PE Sections:

Sections 6
Raw data 123392

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

.text 79872 bytes · 64.7% of section data
MD5 44719bfd92835a43180e92cc061a13cf
.rdata 29696 bytes · 24.1% of section data
MD5 bae7cf885d6821b36915e092587e1bc2
.data 5632 bytes · 4.6% of section data
MD5 92eb1b430caaf1bcc7866afaefc1942b
.crthunk 512 bytes · 0.4% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 2048 bytes · 1.7% of section data
MD5 0803457fad302483202ba4f92c867e1f
.reloc 5632 bytes · 4.6% of section data
MD5 4e4f40522148ce1b9709dc76862b8bb4

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 24f7377d2c472dbf0bd8ff9d6bcfb1a4.
  • 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.