GridinSoft Threat Intelligence

mojo_core.dll file report

Under review File reputation report
MD5 d8e7c0812528c78fd422376631f52105
Latest seen 2025-07-29 23:00:36 (10 months ago)
First seen 2025-07-22 23:00:38 (10 months ago)
Size 1 MB
Signed by Adaptivebee SASU

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-07-22 23:00:38 (10 months ago); latest analysis 2025-07-29 23:00:36 (10 months ago).

Digital signature

Signed by Adaptivebee SASU. 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.

mojo_core.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2025-07-29 23:00:36 (10 months 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.

MD5: d8e7c0812528c78fd422376631f52105
Size: 1 MB
First Published: 2025-07-22 23:00:38 (10 months ago)
Latest Published: 2025-07-29 23:00:36 (10 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-07-29 23:00:36 (10 months ago)
Signed By: Adaptivebee SASU
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.

%localappdata%\urbrowser\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.

Windows 7 100.0%

The most common operating system signal for mojo_core.dll is Windows 7 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.

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 0x000c9a10
Image base 0x0000000180000000

PE Sections:

Sections 9
Raw data 1213952

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

.text 994304 bytes · 81.9% of section data
MD5 1d6bce4df40b372284f6daffa23e3741
.rdata 159232 bytes · 13.1% of section data
MD5 ea5186c083d83ee2aeaa18d48ea567f2
.data 13824 bytes · 1.1% of section data
MD5 525cee76fc10733640cbd6d5b416f18e
.pdata 37888 bytes · 3.1% of section data
MD5 b5462a3ca48193ddc95d7c9e50a7c225
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 82bfa6c2da020f43dba093b1d05a81c9
.gehcont 512 bytes · 0.0% of section data
Uncommon name
MD5 3cadd44482ee5c697abdbfabbf290428
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 6d3e87a3d12f58911501e48bce617787
.reloc 6656 bytes · 0.5% of section data
MD5 07d6c073b430bbbb660d5d44dbdbd92e

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