GridinSoft Threat Intelligence

pepflashplayer.dll.tmp1 file report

Clean record File reputation report
MD5 77f0b20b29f9efaeb94b8142afa7c9d2
Latest seen 2025-03-16 23:04:13 (a year ago)
First seen 2017-05-21 06:06:19 (9 years ago)
Size 16 MB
Publisher Adobe Systems, Inc.
Product Shockwave Flash
Signed by Adobe Systems Incorporated

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-21 06:06:19 (9 years ago); latest analysis 2025-03-16 23:04:13 (a year ago).

Publisher context

Company metadata: Adobe Systems, Inc.. Product metadata: Shockwave Flash.

Digital signature

Signed by Adobe Systems Incorporated. The signature is reported as valid, but signed files can still be bundled or abused.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

File context

pepflashplayer.dll.tmp1 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:13 (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: 77f0b20b29f9efaeb94b8142afa7c9d2
Size: 16 MB
First Published: 2017-05-21 06:06:19 (9 years ago)
Latest Published: 2025-03-16 23:04:13 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2025-03-16 23:04:13 (a year ago)

Overview

Signed By: Adobe Systems Incorporated
Status: Valid

The signature on pepflashplayer.dll.tmp1 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%\360se6\application\ppflash\25_0_0_127
%programfiles%\tencent\wechat
%localappdata%\ballduck\user data\pepperflash\25.0.0.127
%localappdata%\tadolyploteried\pepperflash\25.0.0.127
%localappdata%\amigo\application\56.0.2924.180\pepperflash
%localappdata%\amigo\application\56.0.2924.197\pepperflash
%localappdata%\servesy\pepperflash\25.0.0.127
%localappdata%\footjane\user data\pepperflash\25.0.0.127
%localappdata%\choberk\pepperflash\25.0.0.127
%localappdata%\popiph\pepperflash\25.0.0.127

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

3 observed names
pepflashplayer32_25_0_0_127.dll pepflashplayer.dll pepflashplayer.dll.tmp1

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 pepflashplayer.dll.tmp1 across 66 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Russian Federation
Share 22.1%
Low High activity

The strongest geographic signal for this file is Russian Federation with 22.1% 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 51.2%
Windows 7 38.2%
Windows 8.1 7.6%
Windows 8 1.7%
Windows Server 2012 R2 0.6%
Windows Server 2008 R2 0.5%
Windows Server 2016 0.2%
Windows XP 0.1%

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

pepflashplayer.dll.tmp1 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 0x0084d103
Image base 0x10000000

PE Sections:

Sections 8
Raw data 17776640

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

.text 12849152 bytes · 72.3% of section data
Large raw data
MD5 3f1d14e780eae7da53df0173ba0dd239
.rodata 4608 bytes · 0.0% of section data
MD5 ad6a7b35eaeb57dfb888321e90e6cc1d
.rdata 3596800 bytes · 20.2% of section data
MD5 792595f5a3473fbe47425ffcf8d9a805
.data 815616 bytes · 4.6% of section data
MD5 6bca4d9920f9723943a0c6a2871caeaf
.tls 512 bytes · 0.0% of section data
MD5 8e3343efa9afc26ac6caf49228cbe049
.gfids 1024 bytes · 0.0% of section data
Uncommon name
MD5 db7ce7cc74c3f64cb3f1633874a87dae
.rsrc 2560 bytes · 0.0% of section data
MD5 b0c2ee0b422fb51a1c8c8859fbfc31a9
.reloc 506368 bytes · 2.8% of section data
MD5 e8805681079a4a3eacdf4fdc1d458299

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 77f0b20b29f9efaeb94b8142afa7c9d2.
  • 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.