GridinSoft Threat Intelligence

Substance.mll file report

Under review File reputation report
MD5 c864d64e29a9b1e0315275cdfa629b4d
Latest seen 2022-11-17 23:19:26 (3 years ago)
First seen 2022-11-17 23:19:26 (3 years ago)
Size 102 KB
Signed by Allegorithmic, SAS

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-11-17 23:19:26 (3 years ago); latest analysis 2022-11-17 23:19:26 (3 years ago).

Digital signature

Signed by Allegorithmic, SAS. 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.

Substance.mll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2022-11-17 23:19:26 (3 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: c864d64e29a9b1e0315275cdfa629b4d
Size: 102 KB
First Published: 2022-11-17 23:19:26 (3 years ago)
Latest Published: 2022-11-17 23:19:26 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-11-17 23:19:26 (3 years ago)
Signed By: Allegorithmic, SAS
Status: Valid

The signature on Substance.mll 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%\allegorithmic\substance in maya\2022

ThreatInfo has observed Substance.mll 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 100.0%

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

Substance.mll is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x0000a8a4
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 96256

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

.text 45056 bytes · 46.8% of section data
MD5 8267049813b709e70b3ec9d5e5a115d8
.rdata 46080 bytes · 47.9% of section data
MD5 1ddca72b41d7ce09971a8cd775a8d03b
.data 1024 bytes · 1.1% of section data
MD5 e0336721755159f343870492a72ec1bf
.pdata 2560 bytes · 2.7% of section data
MD5 5cf45a7f18da6362801c53692d91e5b4
.rsrc 512 bytes · 0.5% of section data
MD5 43041985e356ec1bb76514dd6d7a347f
.reloc 1024 bytes · 1.1% of section data
MD5 a0c343a496001044842b98ea1f981dfd

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