GridinSoft Threat Intelligence

LAVAudio.ax file report

Under review File reputation report
MD5 cfc32c08533efe990d5ce46656d9acdd
Latest seen 2024-03-22 23:01:05 (2 years ago)
First seen 2017-05-26 14:07:43 (8 years ago)
Size 251 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-26 14:07:43 (8 years ago); latest analysis 2024-03-22 23:01:05 (2 years ago).

Publisher context

Company metadata: 1f0.de - Hendrik Leppkes. Product metadata: LAV Audio Decoder.

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.

LAVAudio.ax is a Windows file recorded in the ThreatInfo database. It is associated with LAV Audio Decoder. The reported company name is 1f0.de - Hendrik Leppkes. The current detection status is Undefined, based on the latest analysis from 2024-03-22 23:01:05 (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: LAV Audio Decoder
Company Name: 1f0.de - Hendrik Leppkes
MD5: cfc32c08533efe990d5ce46656d9acdd
Size: 251 KB
First Published: 2017-05-26 14:07:43 (8 years ago)
Latest Published: 2024-03-22 23:01:05 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-03-22 23:01:05 (2 years ago)
%programfiles%\baofeng\stormplayer\core\codecs\lavfilters
%programfiles%\baofeng\magicencoder\core\codecs\lavfilters
%programfiles%\baofeng\stormplayer\core\codecs
%programfiles%\baofeng\magicencoder\core\codecs

ThreatInfo has observed LAVAudio.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 75.3%
Windows 7 15.1%
Windows 8.1 6.5%
Windows XP 2.2%
Windows Server 2008 R2 1.1%

The most common operating system signal for LAVAudio.ax is Windows 10 with 75.3% 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.

LAVAudio.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 0x000192f9
Image base 0x10000000

PE Sections:

Sections 6
Raw data 256512

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

.text 171008 bytes · 66.7% of section data
MD5 faa21e4bd01546da532a01a839613141
.rdata 54784 bytes · 21.4% of section data
MD5 a980123afbe95f78e8e81dfda1c979e6
.data 5632 bytes · 2.2% of section data
MD5 e8fca88484f6cda20a904569185816ce
.gfids 512 bytes · 0.2% of section data
Uncommon name
MD5 c19897ca2376dc1dd2b509250086f1d8
.rsrc 13312 bytes · 5.2% of section data
MD5 6b56f0ccf07bd94a0caf2a88990d2728
.reloc 11264 bytes · 4.4% of section data
MD5 6c75f0baae0961b2e779e2a0025b51c1

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