GridinSoft Threat Intelligence

discord_aegis_x86.dll file report

Under review File reputation report
MD5 ce5f0f9bff2113e0a8bd606c1e3d6430
Latest seen 2024-01-01 23:39:07 (2 years ago)
First seen 2024-01-01 23:39:07 (2 years ago)
Size 370 KB
Signed by Discord Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-01-01 23:39:07 (2 years ago); latest analysis 2024-01-01 23:39:07 (2 years ago).

Digital signature

Signed by Discord Inc.. 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.

discord_aegis_x86.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2024-01-01 23:39:07 (2 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: ce5f0f9bff2113e0a8bd606c1e3d6430
Size: 370 KB
First Published: 2024-01-01 23:39:07 (2 years ago)
Latest Published: 2024-01-01 23:39:07 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-01 23:39:07 (2 years ago)
Signed By: Discord Inc.
Status: Valid

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

%commonappdata%\hi\discord\app-1.0.9027\modules\discord_modules-1\discord_modules

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

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

discord_aegis_x86.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 0x00022f40
Image base 0x10000000

PE Sections:

Sections 6
Raw data 358912

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

.text 270848 bytes · 75.5% of section data
MD5 aa52904b107efb2decf87485cff6d489
.rdata 68096 bytes · 19.0% of section data
MD5 7c06b6a74c8e66106b2ce3a011099f5e
.data 6144 bytes · 1.7% of section data
MD5 478036f832065ede793f6a7c5d50ab76
.00cfg 512 bytes · 0.1% of section data
Uncommon name
MD5 339db1252237fa97cbec3e75c3add06e
.tls 512 bytes · 0.1% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.reloc 12800 bytes · 3.6% of section data
MD5 891187dae4585c2d4d44d36b69a2ac45

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