GridinSoft Threat Intelligence

mono-1-vc.dll file report

Under review File reputation report
MD5 aaa7f96d22168f5fc1f4dc7dd182843f
Latest seen 2022-03-15 23:59:39 (4 years ago)
First seen 2018-08-07 18:09:02 (7 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-08-07 18:09:02 (7 years ago); latest analysis 2022-03-15 23:59:39 (4 years ago).

Digital signature

Signed by Unity Technologies ApS. 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-1-vc.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2022-03-15 23:59:39 (4 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.

MD5: aaa7f96d22168f5fc1f4dc7dd182843f
Size: 2 MB
First Published: 2018-08-07 18:09:02 (7 years ago)
Latest Published: 2022-03-15 23:59:39 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-03-15 23:59:39 (4 years ago)
Signed By: Unity Technologies ApS
Status: Valid

The signature on mono-1-vc.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%\webplayer\mono

ThreatInfo has observed mono-1-vc.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 8.1 50.0%
Windows 10 50.0%

The most common operating system signal for mono-1-vc.dll is Windows 8.1 with 50.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-1-vc.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 0x001177f5
Image base 0x10000000

PE Sections:

Sections 5
Raw data 2102272

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

.text 1241600 bytes · 59.1% of section data
MD5 ae447d354ac00a002be4a55614bee043
.rdata 791552 bytes · 37.7% of section data
MD5 c9280e02b3a29adebd1806429279a613
.data 7680 bytes · 0.4% of section data
MD5 09400791d281fa68937f14de6510c0d9
.rsrc 512 bytes · 0.0% of section data
MD5 9468538dcb20dbe86182c349e23f6a73
.reloc 60928 bytes · 2.9% of section data
MD5 af85fe05745b8f097e5e04305351d088

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