GridinSoft Threat Intelligence

libaccess_output_file_plugin.dll file report

Under review File reputation report
MD5 40295e51589ade4eb366971b1a4bbe9f
Latest seen 2025-07-11 23:01:25 (10 months ago)
First seen 2017-05-22 09:02:44 (9 years ago)
Size 24 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-05-22 09:02:44 (9 years ago); latest analysis 2025-07-11 23:01:25 (10 months 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.

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

libaccess_output_file_plugin.dll 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-07-11 23:01:25 (10 months 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: 40295e51589ade4eb366971b1a4bbe9f
Size: 24 KB
First Published: 2017-05-22 09:02:44 (9 years ago)
Latest Published: 2025-07-11 23:01:25 (10 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-07-11 23:01:25 (10 months ago)

Overview

Signed By: VideoLAN
Status: Valid

The signature on libaccess_output_file_plugin.dll 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%\popcorn time\plugins\access_output
%localappdata%\mediaget2\plugins\access_output
%profile%\leg\local settings\application data\mediaget2\plugins\access_output
%commonappdata%\ubar\ubar\modules\vlc\plugins\access_output
%profile%\ser\local settings\application data\mediaget2\plugins\access_output
%profile%\dmin\local settings\application data\mediaget2\plugins\access_output
%programfiles%\videolan\vlc\plugins\access_output
%localappdata%\mediaget2\plugins
%commonappdata%\ubar\ubar\modules\vlc\plugins
%programfiles%\pdpopx\vlc\app\vlc\plugins

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

Geographic signal

Observed country distribution

ThreatInfo has seen libaccess_output_file_plugin.dll across 46 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Russian Federation
Share 69.0%
Low High activity

The strongest geographic signal for this file is Russian Federation with 69.0% 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 58.5%
Windows 7 29.1%
Windows 8.1 10.3%
Windows 8 0.9%
Windows XP 0.6%
Windows Embedded 8.1 0.4%
Windows Server 2016 0.1%

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

libaccess_output_file_plugin.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 0x00001410
Image base 0x6ed80000

PE Sections:

Sections 11
Raw data 16896

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

.text 8192 bytes · 48.5% of section data
MD5 0c8e115aab4924ebedd19303931bf25b
.data 512 bytes · 3.0% of section data
MD5 61022ff6d4d450ef2de0d95a166ed8af
.rdata 2048 bytes · 12.1% of section data
MD5 90c073e612e7908ae4a9e84f8f166bf9
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.edata 512 bytes · 3.0% of section data
MD5 626b608571fc627480b9f9c1b43de759
.idata 2048 bytes · 12.1% of section data
MD5 2a37269fefcbacd47b6c29448627dc2a
.CRT 512 bytes · 3.0% of section data
MD5 6a0910c4f687b5a1092ad5615624f1c1
.tls 512 bytes · 3.0% of section data
MD5 3154d842bb2bf15a314afad2d3dc9883
.rsrc 1024 bytes · 6.1% of section data
MD5 6ad8a1e06ea70004882486e3159db76a
.reloc 1024 bytes · 6.1% of section data
MD5 088ad0085a1efaf665e68bacdace2e7a
/4 512 bytes · 3.0% of section data
Uncommon name
MD5 23dd3243c9255075d1e939f76faa42cf

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 40295e51589ade4eb366971b1a4bbe9f.
  • 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.