GridinSoft Threat Intelligence
mojo_core (2022_06_21 19_31_09 UTC).dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.
First seen 2022-07-16 23:13:31 (3 years ago); latest analysis 2024-06-23 23:01:25 (2 years ago).
Company metadata: Wavesor Software. Product metadata: WaveBrowser.
Signed by Wavesor Software. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
mojo_core (2022_06_21 19_31_09 UTC).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 2024-06-23 23:01:25 (2 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.
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: | fd5d8f6212912299003dbb9d45343fd5 |
| Size: | 1 MB |
| First Published: | 2022-07-16 23:13:31 (3 years ago) |
| Latest Published: | 2024-06-23 23:01:25 (2 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2024-06-23 23:01:25 (2 years ago) |
Overview
| Signed By: | Wavesor Software |
| Status: | Valid |
The signature on mojo_core (2022_06_21 19_31_09 UTC).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:
| %sysdrive%\filehistory\owner\desktop-s6rfeo5\data\c\users\owner\wavesor software\wavebrowser |
| %profile%\wavesor software\wavebrowser |
ThreatInfo has observed mojo_core (2022_06_21 19_31_09 UTC).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 (2022_06_21 19_31_09 UTC).dll across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
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:
The most common operating system signal for mojo_core (2022_06_21 19_31_09 UTC).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 (2022_06_21 19_31_09 UTC).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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
0f3a5678ff82263603917483568719d5
211712ccb09dac013b0f781e82b2d5a9
5c0250eb55ade0cf7f0ba82c9d679e03
fcfe895e51ec88edd030402b9a36d79f
7bae1b438c069f515026d2ca718f6c88
1f354d76203061bfdd5a53dae48d5435
c918b92c64b0d20808324781a2f2b364
98b865efda76d50e8c7d487161bd20d4
c01af380970af58ac42c0a5db0809131
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.