GridinSoft Threat Intelligence

eventlog_provider.dll file report

Under review File reputation report
MD5 c3a746c796205416b7169218fd5e8224
Latest seen 2021-09-25 20:09:00 (4 years ago)
First seen 2020-10-07 13:27:11 (5 years ago)
Size 5 KB
Product Orbitum

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-10-07 13:27:11 (5 years ago); latest analysis 2021-09-25 20:09:00 (4 years ago).

Publisher context

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

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.

eventlog_provider.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 2021-09-25 20:09:00 (4 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: c3a746c796205416b7169218fd5e8224
Size: 5 KB
First Published: 2020-10-07 13:27:11 (5 years ago)
Latest Published: 2021-09-25 20:09:00 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-09-25 20:09:00 (4 years ago)
%localappdata%\orbitum\application

ThreatInfo has observed eventlog_provider.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.

Windows 10 50.0%
Windows 7 33.3%
Windows 8.1 16.7%

The most common operating system signal for eventlog_provider.dll is Windows 10 with 50.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.

eventlog_provider.dll is identified as pe for 64-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point
Image base

PE Sections:

Sections 7
Raw data 4608

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

.text 512 bytes · 11.1% of section data
MD5 eeffcf080b79b09572b06e702ea0d514
.rdata 512 bytes · 11.1% of section data
MD5 44c1a4ab26578b24383b7b158a138bc2
.data 512 bytes · 11.1% of section data
MD5 26a37460c4cc58e6ecd495608a9d2ab6
.pdata 512 bytes · 11.1% of section data
MD5 f18cfc83abe70731b7dfb851905f4e22
.00cfg 512 bytes · 11.1% of section data
Uncommon name
MD5 d74e56f97c1f7baa6b6a935686e656dd
.rsrc 1536 bytes · 33.3% of section data
MD5 f83a6e7b0bc7aed8eb195c8bb2395d9e
.reloc 512 bytes · 11.1% of section data
MD5 af2bf969caf36533c0046cb6f0bec799

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 c3a746c796205416b7169218fd5e8224.
  • 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.