GridinSoft Threat Intelligence

CDXAREADER.AX file report

Under review File reputation report
MD5 214ecdcd1322bf817a870a7c6226da36
Latest seen 2026-01-06 23:00:29 (4 months ago)
First seen 2017-05-21 08:10:32 (9 years ago)
Size 244 KB
Publisher Gabest

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 08:10:32 (9 years ago); latest analysis 2026-01-06 23:00:29 (4 months ago).

Publisher context

Company metadata: Gabest. Product metadata: CDXA Reader Filter.

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.

CDXAREADER.AX is a Windows file recorded in the ThreatInfo database. It is associated with CDXA Reader Filter. The reported company name is Gabest. The current detection status is Undefined, based on the latest analysis from 2026-01-06 23:00:29 (4 months 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.

Product Name: CDXA Reader Filter
Company Name: Gabest
MD5: 214ecdcd1322bf817a870a7c6226da36
Size: 244 KB
First Published: 2017-05-21 08:10:32 (9 years ago)
Latest Published: 2026-01-06 23:00:29 (4 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-01-06 23:00:29 (4 months ago)
%appdata%\multicodec\cdxa reader
%appdata%\vcodec\cdxa reader
%programfiles%\qvodplayer\codecs
%programfiles%\qvodplayer
%programfiles%\gcodec
%programfiles%\howcodec
%appdata%\vcodec
%appdata%\howcodec

ThreatInfo has observed CDXAREADER.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 10 56.0%
Windows 7 36.7%
Windows 8.1 4.6%
Windows XP 1.8%
Windows 8 0.9%

The most common operating system signal for CDXAREADER.AX is Windows 10 with 56.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.

CDXAREADER.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 0x00012fc9
Image base 0x10000000

PE Sections:

Sections 5
Raw data 245760

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

.text 135168 bytes · 55.0% of section data
MD5 a9f444cdc8874bd272f361e7ed64b30a
.rdata 53248 bytes · 21.7% of section data
MD5 d8f26a3901e225cb14ea2eabd9791b56
.data 24576 bytes · 10.0% of section data
MD5 ef15797d5d62c685c70802a004c667f7
.rsrc 4096 bytes · 1.7% of section data
MD5 b17f192bc84ca2eed3f36d8f927f78aa
.reloc 28672 bytes · 11.7% of section data
MD5 f4ff6efb76e264327f5dc31a8d396745

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 214ecdcd1322bf817a870a7c6226da36.
  • 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.