pepflashplayer32_23_0_0_162.dll file report
ThreatInfo file report
pepflashplayer32_23_0_0_162.dll
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-05-21 03:02:01 (8 years ago); latest analysis 2025-03-16 23:04:00 (a year ago).
Company metadata: Adobe Systems, Inc.. Product metadata: Shockwave Flash.
Signed by Adobe Systems Incorporated. The signature is reported as valid, but signed files can still be bundled or abused.
This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
pepflashplayer32_23_0_0_162.dll is a Windows file recorded in the ThreatInfo database. It is associated with Shockwave Flash. The reported company name is Adobe Systems, Inc.. The current detection status is Clean, based on the latest analysis from 2025-03-16 23:04:00 (a year ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | Shockwave Flash |
| Company Name: | Adobe Systems, Inc. |
| MD5: | edabf2c2f7931a91ab23fe7d8a845429 |
| Size: | 16 MB |
| First Published: | 2017-05-21 03:02:01 (8 years ago) |
| Latest Published: | 2025-03-16 23:04:00 (a year ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2025-03-16 23:04:00 (a year ago) |
Overview
| Signed By: | Adobe Systems Incorporated |
| Status: | Valid |
The signature on pepflashplayer32_23_0_0_162.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:
| %appdata%\ucchannel\package\chrome-bin\6.1.2107.204\pepperflash |
| %programfiles%\ucbrowser\application\6.1.2716.5\pepperflash |
| %programfiles%\ucbrowser\application\6.1.2107.204\pepperflash |
| %programfiles%\iqiyi video\pstyle\qyappplugin\falcon |
| %programfiles%\iqiyi video\pstyle\extra_7z\falcon.c228092e1dd372bd27bea8c59a7941ec-updatedefex |
| %programfiles%\ucbrowser\application\6.1.2015.1007\pepperflash |
| %commonappdata%\ubar\ubar\v1.8.0.6 |
| %programfiles%\ucbrowser\application\6.0.1308.1201\pepperflash |
| %localappdata%\ckerferingfujale\pepperflash\22.0.0.209 |
| %programfiles%\ucbrowser\application\5.7.16817.1002\pepperflash |
ThreatInfo has observed pepflashplayer32_23_0_0_162.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.
File Names:
| pepflashplayer.dll |
| pepflashplayer.dll.del |
| pepflashplayer32_23_0_0_162.dll |
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:
| 18.7% | ||
| 14.5% | ||
| 10.5% | ||
| 5.7% | ||
| 4.7% | ||
| 4.6% | ||
| 4.2% | ||
| 3.8% | ||
| 2.1% | ||
| 2.1% | ||
| 1.8% | ||
| 1.7% | ||
| 1.6% | ||
| 1.3% | ||
| 1.2% | ||
| 1.1% | ||
| 1.0% | ||
| 0.9% | ||
| 0.9% | ||
| 0.9% | ||
| 0.9% | ||
| 0.9% | ||
| 0.9% | ||
| 0.7% | ||
| 0.7% | ||
| 0.6% | ||
| 0.5% | ||
| 0.5% | ||
| 0.5% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.4% | ||
| 0.3% | ||
| 0.3% | ||
| 0.3% | ||
| 0.3% | ||
| 0.3% | ||
| 0.3% | ||
| 0.3% | ||
| 0.3% | ||
| 0.3% | ||
| 0.2% | ||
| 0.2% | ||
| 0.2% | ||
| 0.2% | ||
| 0.2% | ||
| 0.2% | ||
| 0.2% | ||
| 0.2% | ||
| 0.2% | ||
| 0.2% | ||
| 0.2% | ||
| 0.2% | ||
| 0.2% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% | ||
| 0.1% |
The strongest geographic signal for this file is Vietnam with 18.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 7 | 47.7% | |
| Windows 10 | 40.4% | |
| Windows 8.1 | 8.6% | |
| Windows 8 | 1.7% | |
| Windows XP | 1.0% | |
| Windows Vista | 0.2% | |
| Windows Server 2012 R2 | 0.2% | |
| Windows Embedded Standard | 0.1% | |
| Windows Embedded 8.1 | 0.1% | |
| Windows Server 2008 R2 | 0.1% | |
| Windows Server 2012 | 0.1% |
The most common operating system signal for pepflashplayer32_23_0_0_162.dll is Windows 7 with 47.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.
Analysis
pepflashplayer32_23_0_0_162.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: | 0x0083494d |
PE Sections:
| Name | Size of data | MD5 |
| .text | 12473344 | b1360992445754bc0a70769af466ea1b |
| .rodata | 4608 | 961b8bc20d84f8383949dde07de5b191 |
| .rdata | 3555328 | f37a07d92722a4128cbd4c6d74e444ff |
| .data | 834560 | 22f71f8989fc07858f0fddd8ac2c8e8f |
| .tls | 512 | bf619eac0cdf3f68d496ea9344137e8b |
| .rsrc | 2560 | a203a41b59dd2902f9a0e9339b8bb6ef |
| .reloc | 723968 | 40ce01599f19c537c13093ce1c6c029c |
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:
