GridinSoft Threat Intelligence

libvlccore.dll file report

Under review File reputation report
MD5 c90976c653fecc24f668f57da0a1cb61
Latest seen 2023-11-28 23:41:51 (2 years ago)
First seen 2017-05-22 11:17:36 (9 years ago)
Size 2 MB
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:36 (9 years ago); latest analysis 2023-11-28 23:41:51 (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.

libvlccore.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:41:51 (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: c90976c653fecc24f668f57da0a1cb61
Size: 2 MB
First Published: 2017-05-22 11:17:36 (9 years ago)
Latest Published: 2023-11-28 23:41:51 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-11-28 23:41:51 (2 years ago)
%programfiles%\fileviewpro
%programfiles%
%sysdrive%\arquivos de programas

ThreatInfo has observed libvlccore.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 46.9%
Windows 7 43.1%
Windows 8.1 6.2%
Windows XP 2.1%
Windows 8 1.0%
Windows Vista 0.7%

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

libvlccore.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 0x6a540000

PE Sections:

Sections 9
Raw data 2262528

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

.text 1155584 bytes · 51.1% of section data
MD5 bea2f0cb324b000f65bd7466a045e416
.data 6656 bytes · 0.3% of section data
MD5 f17b4f0f8af6ed57340464ea24388034
.rdata 1034752 bytes · 45.7% of section data
MD5 5737fa71203fd459dae287ba52058d7a
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 18432 bytes · 0.8% of section data
MD5 5de28816198a79fb5d571795455c175b
.idata 7680 bytes · 0.3% of section data
MD5 1d5b2b408b729b3e2f721240910613f7
.rsrc 1024 bytes · 0.0% of section data
MD5 d57190f98780308982726a24d9613329
.reloc 37888 bytes · 1.7% of section data
MD5 493d79694ae957e575e67b2186670039
.gnu_deb 512 bytes · 0.0% of section data
Uncommon name
MD5 5746fb594f1fca6677b9880f7350356a

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