GridinSoft Threat Intelligence
MaxxAudioAPOShell.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2018-02-17 04:06:45 (8 years ago); latest analysis 2021-01-14 16:20:29 (5 years ago).
Company metadata: Waves Audio Ltd.. Product metadata: MaxxAudio APO Shell.
Signed by Waves Inc. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
MaxxAudioAPOShell.dll is a Windows file recorded in the ThreatInfo database. It is associated with MaxxAudio APO Shell. The reported company name is Waves Audio Ltd.. The current detection status is Undefined, based on the latest analysis from 2021-01-14 16:20:29 (5 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.
File Details
| Product Name: | MaxxAudio APO Shell |
| Company Name: | Waves Audio Ltd. |
| MD5: | 99de7f0838685ce9f4c39e58fee6f48b |
| Size: | 771 KB |
| First Published: | 2018-02-17 04:06:45 (8 years ago) |
| Latest Published: | 2021-01-14 16:20:29 (5 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-01-14 16:20:29 (5 years ago) |
Overview
| Signed By: | Waves Inc |
| Status: | Valid |
The signature on MaxxAudioAPOShell.dll 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.
Common Places:
| %appdata%\driverfinder\backup |
| %appdata%\uniblue\driverscanner\drivers\148483\mb_driver_audio_realtek_w10\realtek_audio |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20161011t131132897575\hdaudio |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20200501t081141684142\hdaudio |
ThreatInfo has observed MaxxAudioAPOShell.dll 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.
Geographic signal
Observed country distribution
ThreatInfo has seen MaxxAudioAPOShell.dll across 4 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 37.5% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for MaxxAudioAPOShell.dll is Windows 7 with 75.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.
Analysis
MaxxAudioAPOShell.dll 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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
ed7b7e90309d9b09547af6c88dd90058
abc6bfd136b6bc16738085ce30bf404c
c8c665fa8e8de7ecb435a82fc86a7e78
30166b05d6874f2f9a6bfebc569a2481
fc7a12988156fef451d9ec3f6c3312f8
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.