GridinSoft Threat Intelligence

mono.dll file report

Under review File reputation report
MD5 c609f84f982e6950abeb67cb4f2f061b
Latest seen 2021-01-10 15:51:51 (5 years ago)
First seen 2018-05-18 05:04:41 (8 years ago)
Size 2 MB
Publisher Unity Technologies
Product libmono

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-05-18 05:04:41 (8 years ago); latest analysis 2021-01-10 15:51:51 (5 years ago).

Publisher context

Company metadata: Unity Technologies. Product metadata: libmono.

Digital signature

Signed by Unity Technologies SF. 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.

mono.dll is a Windows file recorded in the ThreatInfo database. It is associated with libmono. The reported company name is Unity Technologies. The current detection status is Undefined, based on the latest analysis from 2021-01-10 15:51:51 (5 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: libmono
Company Name: Unity Technologies
MD5: c609f84f982e6950abeb67cb4f2f061b
Size: 2 MB
First Published: 2018-05-18 05:04:41 (8 years ago)
Latest Published: 2021-01-10 15:51:51 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-10 15:51:51 (5 years ago)
Signed By: Unity Technologies SF
Status: Valid

The signature on mono.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.

%programfiles%\speedycar\speedycar_data

ThreatInfo has observed mono.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 61.0%
Windows 7 26.2%
Windows 8.1 12.8%

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

mono.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. 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 GUI
Entry point 0x00118905
Image base 0x10000000

PE Sections:

Sections 5
Raw data 2107904

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

.text 1245696 bytes · 59.1% of section data
MD5 7b57f7d56c6b5763b201859f801702c3
.rdata 792064 bytes · 37.6% of section data
MD5 0c246e348375a0057438861cda3f2b33
.data 7680 bytes · 0.4% of section data
MD5 076cb715bac890c0330b47f9e2a9c711
.rsrc 1536 bytes · 0.1% of section data
MD5 8e61f1667e2281484134e4f960fe10ed
.reloc 60928 bytes · 2.9% of section data
MD5 76860be34a61e98567fd5106f4669e7b

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