GridinSoft Threat Intelligence

mojo_core.dll file report

Under review File reputation report
MD5 bf7edc67689ec5ce3193238cb2e33b54
Latest seen 2022-08-26 00:00:16 (3 years ago)
First seen 2022-08-26 00:00:16 (3 years ago)
Size 1 MB
Publisher Wavesor Software
Product WaveBrowser
Signed by Wavesor Software

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-08-26 00:00:16 (3 years ago); latest analysis 2022-08-26 00:00:16 (3 years ago).

Publisher context

Company metadata: Wavesor Software. Product metadata: WaveBrowser.

Digital signature

Signed by Wavesor Software. 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

mojo_core.dll is a Windows file recorded in the ThreatInfo database. It is associated with WaveBrowser. The reported company name is Wavesor Software. The current detection status is Undefined, based on the latest analysis from 2022-08-26 00:00:16 (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.

File Details

Product Name: WaveBrowser
Company Name: Wavesor Software
MD5: bf7edc67689ec5ce3193238cb2e33b54
Size: 1 MB
First Published: 2022-08-26 00:00:16 (3 years ago)
Latest Published: 2022-08-26 00:00:16 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-26 00:00:16 (3 years ago)

Overview

Signed By: Wavesor Software
Status: Valid

The signature on mojo_core.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%\wavebrowser\application

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

mojo_core.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 0x000dc310
Image base 0x0000000180000000

PE Sections:

Sections 12
Raw data 1618944

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

.text 1354240 bytes · 83.6% of section data
MD5 e2abb6f6e95448bee573237613e2c669
.rdata 158208 bytes · 9.8% of section data
MD5 2a876caf66a468710fe94fe13e7d1e98
.data 38400 bytes · 2.4% of section data
MD5 3d5d58b75effe836040eb33a1a4ca211
.pdata 46080 bytes · 2.8% of section data
MD5 b0e2c41b22d5339e6040ad58a654fe08
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 0080ea249df9de29979367f5be740cfb
.gxfg 11264 bytes · 0.7% of section data
Uncommon name
MD5 1bb16904d72df5d1c1440931c58376fe
.retplne 512 bytes · 0.0% of section data
Uncommon name
MD5 8ba86516d84cef220ecd4ff8550b6df0
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.voltbl 512 bytes · 0.0% of section data
Uncommon name
MD5 38997b5aaf2d65bfc172b1a04e671685
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 8924da0322ab2a89095a88e5c74c9647
.rsrc 1536 bytes · 0.1% of section data
MD5 18294b82102781a3c429d6c5195585c6
.reloc 6656 bytes · 0.4% of section data
MD5 ae9424a3abdfb7c12dcec7de57223736

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