GridinSoft Threat Intelligence

libvlccore.dll.DEL.del file report

Under review File reputation report
MD5 edb0f2f19dedbfafb11671724b31c71a
Latest seen 2025-05-02 23:01:23 (a year ago)
First seen 2017-05-21 07:09:15 (9 years ago)
Size 2 MB
Publisher VideoLAN
Product VLC media player

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 07:09:15 (9 years ago); latest analysis 2025-05-02 23:01:23 (a year ago).

Publisher context

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

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

libvlccore.dll.DEL.del 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 2025-05-02 23:01:23 (a year 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: edb0f2f19dedbfafb11671724b31c71a
Size: 2 MB
First Published: 2017-05-21 07:09:15 (9 years ago)
Latest Published: 2025-05-02 23:01:23 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-05-02 23:01:23 (a year ago)

Common Places:

%localappdata%\mediaget2
%profile%\ser\local settings\application data\mediaget2
%profile%\dmin\local settings\application data\mediaget2
%profile%\гор 21\local settings\application data\mediaget2
%localappdata%\mediaget2.$quar
%profile%\dministrator\local settings\application data\mediaget2
%profile%\outude\local settings\application data\mediaget2
%programs%\mediaget2\mediaget2
%profile%\aleraxp32\local settings\application data\mediaget2
%profile%\aster\local settings\application data\mediaget2

ThreatInfo has observed libvlccore.dll.DEL.del 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:

5 observed names
libvlccore.dll libvlccore.dll.quarantined libvlccore.dll.del libvlccore_IObitDel.dll libvlccore.dll.DEL.del

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.

Geographic signal

Observed country distribution

ThreatInfo has seen libvlccore.dll.DEL.del across 49 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Russian Federation
Share 58.7%
Low High activity

The strongest geographic signal for this file is Russian Federation with 58.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 59.4%
Windows 7 27.4%
Windows 8.1 10.0%
Windows 8 1.7%
Windows XP 1.3%
Windows Embedded 8.1 0.1%
Windows Vista 0.1%
Windows Server 2012 R2 0.1%

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

libvlccore.dll.DEL.del 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 0x6a740000

PE Sections:

Sections 11
Raw data 2524160

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

.text 1299968 bytes · 51.5% of section data
MD5 75f4162302cc069f2eca932de75cd337
.data 10752 bytes · 0.4% of section data
MD5 10873ded29586acf69dfe0de7d2a50a8
.rdata 1143296 bytes · 45.3% of section data
MD5 007363b2ecfcd51b8aa18990319af5a4
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 18944 bytes · 0.8% of section data
MD5 81c1cf2228eb11637ced374c6c774120
.idata 8192 bytes · 0.3% of section data
MD5 a57ed25fced55183c991c04f0a238208
.CRT 512 bytes · 0.0% of section data
MD5 462c16668f454abc4105e7c910a13f05
.tls 512 bytes · 0.0% of section data
MD5 d621d35303adcac8c6a26fa3fd80453b
.rsrc 1536 bytes · 0.1% of section data
MD5 987592108e79ab333f28d7dbe0669c8b
.reloc 39936 bytes · 1.6% of section data
MD5 ab8d001d6688bdc70dbde041979bfcde
/4 512 bytes · 0.0% of section data
Uncommon name
MD5 d15e3bcba88d7dfa9cc9058e63963e76

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