pepflashplayer.dll file report

MD5 db4106aacd3bbaae77c226c1f6847e85
Latest seen 2021-10-29 20:11:52 (4 years ago)
First seen 2020-05-13 11:28:10 (5 years ago)
Size 17 MB
Publisher Adobe
Product Shockwave Flash
Signed by Adobe Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-05-13 11:28:10 (5 years ago); latest analysis 2021-10-29 20:11:52 (4 years ago).

Publisher context

Company metadata: Adobe. Product metadata: Shockwave Flash.

Digital signature

Signed by Adobe Inc.. 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.

pepflashplayer.dll is a Windows file recorded in the ThreatInfo database. It is associated with Shockwave Flash. The reported company name is Adobe. The current detection status is Undefined, based on the latest analysis from 2021-10-29 20:11:52 (4 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: Shockwave Flash
Company Name: Adobe
MD5: db4106aacd3bbaae77c226c1f6847e85
Size: 17 MB
First Published: 2020-05-13 11:28:10 (5 years ago)
Latest Published: 2021-10-29 20:11:52 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-10-29 20:11:52 (4 years ago)
Signed By: Adobe Inc.
Status: Valid

The signature on pepflashplayer.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.

%localappdata%\webdiscoverbrowser\user data\pepperflash
%localappdata%\webdiscoverbrowser\user data\pepperflash
%appdata%\view\chrome\newprofile\pepperflash
%localappdata%\elements browser\user data\pepperflash
%localappdata%\webdiscoverbrowser\user data\pepperflash
%localappdata%\webdiscoverbrowser\user data\pepperflash
%localappdata%\webdiscoverbrowser\user data\pepperflash

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

28.6%
28.6%
14.3%
14.3%
14.3%

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

Windows 10 85.7%
Windows 7 14.3%

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

pepflashplayer.dll is identified as pe for 32 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.

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x0087b5a5

PE Sections:

Name Size of data MD5
.text 12892160 62a8f44fb8a803ffcf2755657f91e8b7
.rodata 4608 6d4452b7e2a3c0402cef292230301aaa
.rdata 3694080 05df019cf9db8236a6246d652ab7b5e6
.data 820224 ea82828cfa27abbdc908c664e4532e50
.tls 512 8e3343efa9afc26ac6caf49228cbe049
.gfids 1024 7fdb2a996a928ed40102992f4d1ef6e6
.rsrc 2560 9ca168ce8f65ba2be38f616a7491efbf
.reloc 509440 c6498dc92d2dfe8e2bd0a68ddd26b595

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.

More information: