mono.dll threat report

MD5 eb1ce1faab94352a268f870bad0bf33f
Latest seen 2023-12-30 23:02:09 (2 years ago)
First seen 2023-12-30 23:02:09 (2 years ago)
Size 28 MB
Publisher Unity Technologies
Product libmono

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2023-12-30 23:02:09 (2 years ago)
File hash
eb1ce1faab94352a268f870bad0bf33f
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2023-12-30 23:02:09 (2 years ago); latest analysis 2023-12-30 23:02:09 (2 years ago).

Publisher context

Company metadata: Unity Technologies. Product metadata: libmono.

Digital signature

Signed by 浙江无端科技股份有限公司. 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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

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 Trojan.Heur!, based on the latest analysis from 2023-12-30 23:02:09 (2 years ago).

If mono.dll appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Heur!.

Product Name: libmono
Company Name: Unity Technologies
MD5: eb1ce1faab94352a268f870bad0bf33f
Size: 28 MB
First Published: 2023-12-30 23:02:09 (2 years ago)
Latest Published: 2023-12-30 23:02:09 (2 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2023-12-30 23:02:09 (2 years ago)
mono.dll detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

Signed By: 浙江无端科技股份有限公司
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%\battle teams 2\client\hallclient_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.

100.0%

The strongest geographic signal for this file is Russia with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for mono.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.

mono.dll is identified as pe for 64 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000180000000
Entry Address: 0x00568220

PE Sections:

Name Size of data MD5
.text 1630208 a77ff92d70dd526386f9e2548cbc1ec1
.rdata 869376 37a8d494491ac0570c0942903e23909f
.data 11776 46b2f1dbfb6895e4dd4cc24ebd15c9cb
.pdata 57856 c29fcc2522007485e884c59053f168af
text 7680 1c98b73a50849329edad7ad002438208
data 25600 1b9d5d9973fb2ae1bf9cbae6bd651bf5
.text 428544 3867bf570cf853f19a6b135e845ae236
.rdata 222720 9d07c1e7a2fa99d7f7295c4de4866ef1
.data 71168 9cf6991fefade4a982a1a0f896a5b4d0
.pdata 24064 90cb48658f7a17db79f9d01c3cabbf57
.gfids 512 6fbdafb24b30f51da17fc0e24cd18f0c
.tls 512 1f354d76203061bfdd5a53dae48d5435
.edata2 29696 7754be2445b12165a241ec8e1c18ca06
.idata2 11776 8fa63dc5f152addb9420180e226d1e02
.rsrc2 25840128 87098a310496b31bfa683885e7818aa7
.reloc 27136 eb30a39e9c6ab598e8f096355f4c2cde
.tvm0 118784 5e1ea873f9044a120308e9893d2daba8
.reloc 27136 611b96ee6e8bbb083ad664146d12d9ab

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.

More information: