GridinSoft Threat Intelligence

pepflashplayer.dlltmp file report

Clean record File reputation report
MD5 bae96dd6aa3e81fe5898ac4ce70f0dc2
Latest seen 2021-03-03 16:29:04 (5 years ago)
First seen 2017-05-21 14:10:21 (8 years ago)
Size 16 MB
Product Shockwave Flash

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-21 14:10:21 (8 years ago); latest analysis 2021-03-03 16:29:04 (5 years 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.

pepflashplayer.dlltmp 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 2021-03-03 16:29:04 (5 years 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.

Product Name: Shockwave Flash
Company Name: Adobe Systems, Inc.
MD5: bae96dd6aa3e81fe5898ac4ce70f0dc2
Size: 16 MB
First Published: 2017-05-21 14:10:21 (8 years ago)
Latest Published: 2021-03-03 16:29:04 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-03-03 16:29:04 (5 years ago)
Signed By: Adobe Systems Incorporated
Status: Valid

The signature on pepflashplayer.dlltmp 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%\hotdear\user data\pepperflash\23.0.0.166
%localappdata%\coqosy\pepperflash\23.0.0.166
%localappdata%\cerzick\pepperflash\23.0.0.166
%localappdata%\plmckatertak\pepperflash\23.0.0.166
%localappdata%\hotjob\user data\pepperflash\23.0.0.166
%localappdata%\amigo\application\50.0.2661.240\pepperflash
%localappdata%\drjiinggukering\pepperflash\23.0.0.166
%localappdata%\fuhigenetuy\pepperflash\23.0.0.166
%localappdata%\qsoseploqge\pepperflash\23.0.0.166
%localappdata%\jamjob\user data\pepperflash\23.0.0.166

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

pepflashplayer.dll pepflashplayer32_23_0_0_162.dll pepflashplayer.dlltmp

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.

20.4%
12.5%
8.3%
6.7%
5.6%
4.9%
4.5%
4.0%
3.8%
3.8%
2.9%
2.5%
1.8%
1.8%
1.6%
1.3%
1.1%
1.1%
1.1%
0.9%
0.9%
0.9%
0.7%
0.7%
0.7%
0.4%
0.4%
0.4%
0.4%
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.2%
0.2%
0.2%
0.2%

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

Windows 10 60.7%
Windows 7 28.0%
Windows 8.1 8.6%
Windows 8 1.3%
Windows Server 2012 0.7%
Windows Server 2012 R2 0.4%
Windows XP 0.2%

The most common operating system signal for pepflashplayer.dlltmp is Windows 10 with 60.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.dlltmp 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 0x008481b0
Image base 0x10000000

PE Sections:

Sections 8
Raw data 17746944

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

.text 12822016 bytes · 72.2% of section data
Large raw data
MD5 94d4e03060a5e1142b3c99fa8e86a046
.rodata 4608 bytes · 0.0% of section data
MD5 ad6a7b35eaeb57dfb888321e90e6cc1d
.rdata 3593728 bytes · 20.2% of section data
MD5 ba03e7de17c9fd4a4eee42198783c35a
.data 815616 bytes · 4.6% of section data
MD5 1ad9e2a347a9d952f649bee5659269c6
.tls 512 bytes · 0.0% of section data
MD5 8e3343efa9afc26ac6caf49228cbe049
.gfids 1024 bytes · 0.0% of section data
Uncommon name
MD5 1ee9b9d28769004b213b9ae40ac722bc
.rsrc 2560 bytes · 0.0% of section data
MD5 f86cfb99d02e7f08319d817ef5125f0f
.reloc 506880 bytes · 2.9% of section data
MD5 784c438e7a954d777ea99fe74ba0fa92

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