GridinSoft Threat Intelligence

libau_plugin.dll file report

Under review File reputation report
MD5 003aec04d21c790f5cdec00b25dce187
Latest seen 2024-06-20 23:00:30 (2 years ago)
First seen 2018-01-13 21:20:47 (8 years ago)
Size 35 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-01-13 21:20:47 (8 years ago); latest analysis 2024-06-20 23:00:30 (2 years ago).

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.

File context

libau_plugin.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2024-06-20 23:00:30 (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.

File Details

MD5: 003aec04d21c790f5cdec00b25dce187
Size: 35 KB
First Published: 2018-01-13 21:20:47 (8 years ago)
Latest Published: 2024-06-20 23:00:30 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-06-20 23:00:30 (2 years ago)

Common Places:

%programfiles%\hdplayer\plugins\vlc

ThreatInfo has observed libau_plugin.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.

Geography:

6 observed countries
58.8%
11.8%
11.8%
5.9%
5.9%
5.9%

The strongest geographic signal for this file is Turkey with 58.8% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 7 64.7%
Windows 10 35.3%

The most common operating system signal for libau_plugin.dll is Windows 7 with 64.7% 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

libau_plugin.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x000010c0
Image base 0x6fec0000

PE Sections:

Sections 8
Raw data 35328

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

.text 28672 bytes · 81.2% of section data
MD5 84a9b32ee7519d618758c984760d44fb
.data 512 bytes · 1.4% of section data
MD5 70655b3e5694fcccbd44f0ff4740e720
.rdata 2048 bytes · 5.8% of section data
MD5 e0162dfa1ef496070d4d5310d20f1487
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 512 bytes · 1.4% of section data
MD5 22b06b786aa1628aa48705f3e0769b70
.idata 2048 bytes · 5.8% of section data
MD5 ffd476092d30ca8bb247e7445d0c4858
.reloc 1024 bytes · 2.9% of section data
MD5 86396e5e4d17b0b8a8f24f9ee0c6946f
.gnu_deb 512 bytes · 1.4% of section data
Uncommon name
MD5 80c7c2d2a642a9d4c115deb568dc1f3b

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 003aec04d21c790f5cdec00b25dce187.
  • 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.