GridinSoft Threat Intelligence

cdxareader.ax file report

Under review File reputation report
MD5 673305ebc836948158fec4209099dcb7
Latest seen 2024-03-22 23:01:00 (2 years ago)
First seen 2017-05-26 14:07:39 (9 years ago)
Size 272 KB
Publisher Gabest

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-26 14:07:39 (9 years ago); latest analysis 2024-03-22 23:01:00 (2 years 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 2024-03-22 23:01:00 (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.

Product Name: CDXA Reader Filter
Company Name: Gabest
MD5: 673305ebc836948158fec4209099dcb7
Size: 272 KB
First Published: 2017-05-26 14:07:39 (9 years ago)
Latest Published: 2024-03-22 23:01:00 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-03-22 23:01:00 (2 years ago)
%programfiles%\baofeng\stormplayer\core\codecs
%programfiles%\baofeng\magicencoder\core\codecs
%programfiles%\baofeng\stormplayer\core
%programfiles%\baofeng\magicencoder\core

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 79.6%
Windows 7 12.9%
Windows 8.1 5.4%
Windows XP 2.2%

The most common operating system signal for cdxareader.ax is Windows 10 with 79.6% 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 0x0001519f
Image base 0x10000000

PE Sections:

Sections 5
Raw data 274432

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

.text 159744 bytes · 58.2% of section data
MD5 eb5ff4b6ad67a034e6d4d41f4995e5e0
.rdata 57344 bytes · 20.9% of section data
MD5 a69364b2b42b7e565462227b135c42c9
.data 24576 bytes · 9.0% of section data
MD5 5f1205060d2b0c6365fed8fb8786c742
.rsrc 4096 bytes · 1.5% of section data
MD5 4b3b36842b3d9bc0287effb77588fa86
.reloc 28672 bytes · 10.4% of section data
MD5 3290022c5ecea601f6c16b606af7ae59

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 673305ebc836948158fec4209099dcb7.
  • 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.