GridinSoft Threat Intelligence

eventlog_provider.dll file report

Under review File reputation report
MD5 f470666c0c3dbd8a011992345f9195cb
Latest seen 2022-08-03 23:52:08 (3 years ago)
First seen 2020-11-13 04:06:59 (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-11-13 04:06:59 (5 years ago); latest analysis 2022-08-03 23:52:08 (3 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 2022-08-03 23:52:08 (3 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: f470666c0c3dbd8a011992345f9195cb
Size: 5 KB
First Published: 2020-11-13 04:06:59 (5 years ago)
Latest Published: 2022-08-03 23:52:08 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-03 23:52:08 (3 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.

33.3%
33.3%
33.3%

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

Windows 10 66.7%
Windows 7 33.3%

The most common operating system signal for eventlog_provider.dll is Windows 10 with 66.7% 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 32-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 32-bit
Subsystem Windows CUI
Entry point
Image base

PE Sections:

Sections 6
Raw data 4096

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

.text 512 bytes · 12.5% of section data
MD5 cfa0dc7b6ae2cc99af2881e9e9945726
.rdata 512 bytes · 12.5% of section data
MD5 a2ea931c871624b2d269afde4da23463
.data 512 bytes · 12.5% of section data
MD5 81c3ad2179d63c737193143995ffe71d
.00cfg 512 bytes · 12.5% of section data
Uncommon name
MD5 a62196f639a167621a9b44552dcaa33d
.rsrc 1536 bytes · 37.5% of section data
MD5 984da1f5bfd89a6bb899b970acec7fab
.reloc 512 bytes · 12.5% of section data
MD5 15f9463aa5f7f00d3b0fe4c955b33183

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