GridinSoft Threat Intelligence

axvlc.dll file report

Under review File reputation report
MD5 0ff21a9a01f69e8ff021db0da15eaece
Latest seen 2023-11-28 23:43:27 (2 years ago)
First seen 2017-05-22 11:17:44 (9 years ago)
Size 315 KB
Publisher the VideoLAN Team

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 11:17:44 (9 years ago); latest analysis 2023-11-28 23:43:27 (2 years ago).

Publisher context

Company metadata: the VideoLAN Team.

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.

axvlc.dll is a Windows file recorded in the ThreatInfo database. The reported company name is the VideoLAN Team. The current detection status is Undefined, based on the latest analysis from 2023-11-28 23:43:27 (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.

Company Name: the VideoLAN Team
MD5: 0ff21a9a01f69e8ff021db0da15eaece
Size: 315 KB
First Published: 2017-05-22 11:17:44 (9 years ago)
Latest Published: 2023-11-28 23:43:27 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-11-28 23:43:27 (2 years ago)
%programfiles%\fileviewpro
%programfiles%
%sysdrive%\arquivos de programas

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

Windows 10 45.7%
Windows 7 43.4%
Windows 8.1 7.2%
Windows XP 2.0%
Windows 8 1.0%
Windows Vista 0.7%

The most common operating system signal for axvlc.dll is Windows 10 with 45.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.

axvlc.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 0x6b640000

PE Sections:

Sections 9
Raw data 322048

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

.text 177664 bytes · 55.2% of section data
MD5 c27d0d25fd1dbe29b9d40c1e99a8ffd9
.data 19456 bytes · 6.0% of section data
MD5 a2146746b15a8369378d8a387510ab8c
.rdata 25088 bytes · 7.8% of section data
MD5 23ddcc8a024ae4e98bca0e08eda56bb5
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 512 bytes · 0.2% of section data
MD5 eeb29c6ad2365382aae1a4db03cf5c57
.idata 8704 bytes · 2.7% of section data
MD5 9d88d000474b1fb6c21e043c91b5fab9
.rsrc 80896 bytes · 25.1% of section data
MD5 6aa28d50dcac2cf4befe0705b2b147e2
.reloc 9216 bytes · 2.9% of section data
MD5 19c1b64732c7c9c37c6dda2cffd1a18e
.gnu_deb 512 bytes · 0.2% of section data
Uncommon name
MD5 f1227b647e01a61928d2b38d7effdc56

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 0ff21a9a01f69e8ff021db0da15eaece.
  • 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.