GridinSoft Threat Intelligence

chrome.dll file report

Under review File reputation report
MD5 294a2ea9dab97c3ab099f9aeaa1864b3
Latest seen 2024-01-03 23:20:47 (2 years ago)
First seen 2024-01-03 23:20:47 (2 years ago)
Size 38 MB
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:20:47 (2 years ago); latest analysis 2024-01-03 23:20:47 (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.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:20:47 (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: 294a2ea9dab97c3ab099f9aeaa1864b3
Size: 38 MB
First Published: 2024-01-03 23:20:47 (2 years ago)
Latest Published: 2024-01-03 23:20:47 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-03 23:20:47 (2 years ago)
Signed By: Bergarius Limited
Status: Valid

The signature on chrome.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.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.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 0x019f0026
Image base 0x01c30000

PE Sections:

Sections 7
Raw data 40515584

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

.text 33156096 bytes · 81.8% of section data
Large raw data
MD5 b4f8b0056236bc07d7d91891dd16cacf
.rdata 5839872 bytes · 14.4% of section data
Large raw data
MD5 3b967ab94bc5e3bae416f2287d31bbf0
.data 170496 bytes · 0.4% of section data
MD5 ce5b77e6853d16cce45e3f11794293a7
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
_RDATA 4608 bytes · 0.0% of section data
Uncommon name
MD5 a771ee6d53f14b3267b440ff74aa2697
.rsrc 137216 bytes · 0.3% of section data
MD5 13041fbe359ae1f248ad317070c4e991
.reloc 1206784 bytes · 3.0% of section data
MD5 f28bf6ad10be5ba23efb333d02e24441

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 294a2ea9dab97c3ab099f9aeaa1864b3.
  • 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.