GridinSoft Threat Intelligence

VLC media player file report

Under review File reputation report
MD5 dc404f53e781e4f865a67d79a8ba4aa3
Latest seen 2024-04-01 23:07:25 (2 years ago)
First seen 2017-06-27 09:09:47 (8 years ago)
Size 106 KB
Publisher VideoLAN
Signed by VideoLAN

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-06-27 09:09:47 (8 years ago); latest analysis 2024-04-01 23:07:25 (2 years ago).

Publisher context

Company metadata: VideoLAN. Product metadata: VLC media player.

Digital signature

Signed by VideoLAN. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

VLC media player is a Windows file recorded in the ThreatInfo database. It is associated with VLC media player. The reported company name is VideoLAN. The current detection status is Undefined, based on the latest analysis from 2024-04-01 23:07:25 (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: VLC media player
Company Name: VideoLAN
MD5: dc404f53e781e4f865a67d79a8ba4aa3
Size: 106 KB
First Published: 2017-06-27 09:09:47 (8 years ago)
Latest Published: 2024-04-01 23:07:25 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-04-01 23:07:25 (2 years ago)
Signed By: VideoLAN
Status: Valid

The signature on VLC media player 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.

%programfiles%\tencent\weiyundisk\bin\plugins\demux
%appdata%\zona\plugins\zvlcj\plugins\demux
%appdata%\systweak\advanced system~protector\quarantine\pua.zona
%programfiles%\tencent\weiyundisk\weiyundisk\bin\plugins\demux
%programfiles%\tencent\weiyundisk\bin\plugins
%programfiles%\tencent\weiyundisk\weiyundisk\bin\plugins
%programfiles%\tencent\weiyundisk\weiyundisk\weiyundisk\bin\plugins
%localappdata%\catalinagroup\citrio\user data\default\extensions\hjinflocgjpjihbgdlipilmjlbkjkmak\0.6.7_0\binaries\win\plugins

ThreatInfo has observed VLC media player 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.

libavi_plugin.dll libavi_plugin.dll.bak dc404f53e781e4f865a67d79a8ba4aa3_080717014226698_543333299.dat

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Windows 10 75.9%
Windows 7 22.4%
Windows 8.1 1.7%

The most common operating system signal for VLC media player is Windows 10 with 75.9% 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.

VLC media player 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 0x00001410
Image base 0x6e240000

PE Sections:

Sections 11
Raw data 100352

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

.text 81408 bytes · 81.1% of section data
MD5 8a79d53a96603ed5add8c6720a15c6d7
.data 512 bytes · 0.5% of section data
MD5 527f88d13a610b4e0996f25911082680
.rdata 10240 bytes · 10.2% of section data
MD5 727e39d520471faf12db518647962b99
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 512 bytes · 0.5% of section data
MD5 953b9c4603569359c890d35bec6fbf6b
.idata 2560 bytes · 2.6% of section data
MD5 c77cc2bd50eec5dfde94402bcf6c9a7a
.CRT 512 bytes · 0.5% of section data
MD5 d176bff290944582ea54b840998845fb
.tls 512 bytes · 0.5% of section data
MD5 8acb1bc26fa844e8371593aa668fcd6f
.rsrc 1024 bytes · 1.0% of section data
MD5 c2ed7eb7acf825fff25bd7471bb6a040
.reloc 2560 bytes · 2.6% of section data
MD5 a1b4f0bb45bbd8177b4bcf68fbfa315b
/4 512 bytes · 0.5% of section data
Uncommon name
MD5 423d20a1f404efcb8587da77b57ae8c4

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