GridinSoft Threat Intelligence

VLC media player file report

Under review File reputation report
MD5 005f655503198de0e5bc1d3a89a0becd
Latest seen 2024-04-01 23:07:31 (2 years ago)
First seen 2017-06-27 09:09:53 (8 years ago)
Size 30 KB
Publisher VideoLAN
Product VLC media player
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:53 (8 years ago); latest analysis 2024-04-01 23:07:31 (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.

File context

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:31 (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

Product Name: VLC media player
Company Name: VideoLAN
MD5: 005f655503198de0e5bc1d3a89a0becd
Size: 30 KB
First Published: 2017-06-27 09:09:53 (8 years ago)
Latest Published: 2024-04-01 23:07:31 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-04-01 23:07:31 (2 years ago)

Overview

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.

Common Places:

%programfiles%\tencent\weiyundisk\bin\plugins\video_filter
%appdata%\zona\plugins\zvlcj\plugins\video_filter
%appdata%\systweak\advanced system~protector\quarantine\pua.zona
%programfiles%\tencent\weiyundisk\weiyundisk\bin\plugins\video_filter
%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.

File Names:

3 observed names
libgradfun_plugin.dll libgradfun_plugin.dll.bak 005f655503198de0e5bc1d3a89a0becd_080717014237419_2015815768.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.

Geography:

16 observed countries
20.7%
20.7%
15.5%
13.8%
5.2%
3.4%
3.4%
3.4%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%

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

OS Version:

Windows 10 76.3%
Windows 7 22.0%
Windows 8.1 1.7%

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

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 0x68ec0000

PE Sections:

Sections 11
Raw data 23040

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

.text 14848 bytes · 64.4% of section data
MD5 7520e22084423c83b7fffb3e7ffcf8f9
.data 512 bytes · 2.2% of section data
MD5 7ac68db18db570d34c0fa15cec70e4b8
.rdata 1536 bytes · 6.7% of section data
MD5 5ff1b84b38022b564d46bd6cc43c854d
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 512 bytes · 2.2% of section data
MD5 edc7ef9ea23ba625af9288334934c441
.idata 2048 bytes · 8.9% of section data
MD5 74ce0993d7ffaab085804d3d3447685e
.CRT 512 bytes · 2.2% of section data
MD5 271e918ce55fc62a2d8af8576623ad69
.tls 512 bytes · 2.2% of section data
MD5 a381d8e062bd9318dc0fcc3ac787256e
.rsrc 1024 bytes · 4.4% of section data
MD5 fdaece0823f7fdf8f40cbb2efd41aed6
.reloc 1024 bytes · 4.4% of section data
MD5 9bd0e50435659a5ae25d9d347a971a81
/4 512 bytes · 2.2% of section data
Uncommon name
MD5 b6fc42683a2af1957244585630bfde7b

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 005f655503198de0e5bc1d3a89a0becd.
  • 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.