How to remove GameAssembly.dll
GameAssembly.dll
The module GameAssembly.dll has been detected as Trojan.Heur!
GameAssembly.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Trojan.Heur!, based on the latest analysis from 2026-03-18 23:00:45 (2 months ago).
If GameAssembly.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!.
File Details
| MD5: | 5a688a555cf62d13ac62d76ab5aaf7a3 |
| Size: | 30 MB |
| First Published: | 2026-03-18 23:00:45 (2 months ago) |
| Latest Published: | 2026-03-18 23:00:45 (2 months ago) |
| Status: | Trojan.Heur! (on last analysis) | |
| Analysis Date: | 2026-03-18 23:00:45 (2 months ago) |
Overview
| Signed By: | ASOBIMO,Inc. |
| Status: | Valid |
The signature on GameAssembly.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%\steamlibrary\steamapps\common |
ThreatInfo has observed GameAssembly.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.
Geography:
| 100.0% |
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:
| Windows 10 | 100.0% |
The most common operating system signal for GameAssembly.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
GameAssembly.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: | 0x03936200 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 903680 | e0be7714c67207583836c808265de1c4 |
| il2cpp | 15147520 | a0c429a1fa3819a96e5c17900e27ebd2 |
| .rdata | 8071680 | 7fe8a4dedafab168cc3c5110754e752c |
| .data | 3096576 | c8b115594223df1596391ec876b859a6 |
| .pdata | 1941504 | 27d9cadcdfb7e998cd93f1a62588d7de |
| _RDATA | 512 | ce52dc6f6b95df26cefe035ef0ff654a |
| .reloc | 811520 | dea9d09184bc8c838f59b08bcd173c42 |
| 2493952 | 3a1536e8bb0435be654b619517f8ee8b |
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:
