GridinSoft Threat Intelligence

LAVSplitter.ax file report

Under review File reputation report
MD5 4b3ac4377e8ba8c6b15a06b45b145fdc
Latest seen 2024-03-22 23:01:05 (2 years ago)
First seen 2017-05-28 06:08:06 (9 years ago)
Size 516 KB
Product LAV Splitter

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-28 06:08:06 (9 years ago); latest analysis 2024-03-22 23:01:05 (2 years ago).

Publisher context

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

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.

LAVSplitter.ax is a Windows file recorded in the ThreatInfo database. It is associated with LAV Splitter. 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 Splitter
Company Name: 1f0.de - Hendrik Leppkes
MD5: 4b3ac4377e8ba8c6b15a06b45b145fdc
Size: 516 KB
First Published: 2017-05-28 06:08:06 (9 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\magicencoder\core\codecs
%programfiles%\baofeng\stormplayer\core\codecs

ThreatInfo has observed LAVSplitter.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 53.8%
Windows 7 30.8%
Windows XP 7.7%
Windows 8.1 7.7%

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

LAVSplitter.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 0x0003be32
Image base 0x10000000

PE Sections:

Sections 6
Raw data 527360

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

.text 371712 bytes · 70.5% of section data
MD5 73563afb67f2299bbc1880fe3d845064
.rdata 102400 bytes · 19.4% of section data
MD5 b8e99e5cd60420aec19367199dde1b96
.data 18944 bytes · 3.6% of section data
MD5 32b08fc9c99e339cfb5ad7d9a82c5c92
.tls 512 bytes · 0.1% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 9728 bytes · 1.8% of section data
MD5 b3f59157af63d1cd4fdb0a0cfca61b19
.reloc 24064 bytes · 4.6% of section data
MD5 21148b0f7b8ea5956530d899ac7a5930

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 4b3ac4377e8ba8c6b15a06b45b145fdc.
  • 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.