GridinSoft Threat Intelligence

CoreAAC.ax file report

Under review File reputation report
MD5 615e81668db46318753231efa25734ba
Latest seen 2023-11-09 23:16:08 (2 years ago)
First seen 2017-12-12 14:07:37 (8 years ago)
Size 317 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-12-12 14:07:37 (8 years ago); latest analysis 2023-11-09 23:16:08 (2 years ago).

Digital signature

Signed by Shenzhen Enode Technology Co., Ltd.. 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.

CoreAAC.ax is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2023-11-09 23:16:08 (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: 615e81668db46318753231efa25734ba
Size: 317 KB
First Published: 2017-12-12 14:07:37 (8 years ago)
Latest Published: 2023-11-09 23:16:08 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-11-09 23:16:08 (2 years ago)
Signed By: Shenzhen Enode Technology Co., Ltd.
Status: Valid

The signature on CoreAAC.ax 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%\hi\hiplayer\1.143.0.0

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

The most common operating system signal for CoreAAC.ax is Windows 7 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.

CoreAAC.ax 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 0x0000b421
Image base 0x10000000

PE Sections:

Sections 5
Raw data 315392

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

.text 151552 bytes · 48.1% of section data
MD5 857ef7bfab32008058ba5223e5685acd
.rdata 126976 bytes · 40.3% of section data
MD5 4da526c9924f5d0ed9ab7cdfaaabe334
.data 12288 bytes · 3.9% of section data
MD5 7b326dfa2a9442fd48ddc4e5882d6a85
.rsrc 16384 bytes · 5.2% of section data
MD5 dee5f7804b7eec80a321f54ae77a37d1
.reloc 8192 bytes · 2.6% of section data
MD5 37421b83f26f92bb9ee7320db02342f2

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 615e81668db46318753231efa25734ba.
  • 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.