Is Pekora.exe safe?
No engines detected malware across broad historical exposure, although unsigned code, destructive-technique mappings, and one suspicious contacted domain warrant ordinary installation caution.
The file received no detections from 75 engines, including no tier-1 flags, despite 2,267 submissions from 1,864 sources. One sandbox produced no malicious verdict, but the executable is unsigned, contacted a domain with a suspicious reputation, and triggered T1485 and T1486 mappings, so it should come only from the expected project source.
a3b3a175d5f15c7794…245128f72015b3Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
The file received no detections from 75 engines, including no tier-1 flags, despite 2,267 submissions from 1,864 sources. One sandbox produced no malicious verdict, but the executable is unsigned, contacted a domain with a suspicious reputation, and triggered T1485 and T1486 mappings, so it should come only from the expected project source.
No antivirus engine flagged this sample, and 15 tier-1 engines reported no detection. That result is particularly persuasive because the file has circulated through 1,864 sources and accumulated 2,267 submissions over 222 days. One completed sandbox did not produce a malicious verdict, and none of the ten inspected dropped files was identified as malicious, although their individual verdicts remain unknown. The main cautions are the missing digital signature, technique mappings T1485 and T1486, and contact with www.pekora.zip, which carries a suspicious cached reputation. These counter-signals justify source verification but do not outweigh the broad, detection-free history and absence of a confirmed malicious family, host, child, or sandbox result.
What We Detected
The sample received 0 malicious and 0 suspicious results from 75 antivirus engines. Fifteen tier-1 engines reported no detection, and no engine family consensus, hacktool label, packing indicator, or brand mismatch was present. The file is also widely observed, with 2,267 submissions from 1,864 sources over 222 days.
Threat Behavior
One completed sandbox run did not issue a malicious verdict. It observed installation activity, downloads, registry changes, and contact with setup.pekora.zip, www.pekora.zip, and api.pekora.zip. The three contacted domains were covered by the host-reputation check: none was known malicious, but www.pekora.zip was marked suspicious. Technique mappings included T1485 and T1486; these are concerning labels, yet the recorded file operations and sandbox conclusion do not independently confirm destructive execution. Ten dropped files were inspected without a malicious finding, though their individual verdicts remain unknown.
What To Do Now
Confirm that the SHA-256 a3b3a175d5f15c7794cf51412dd54073efaa0b98376ba0b906245128f72015b3 came from the expected Pekora distribution channel before running it. Keep endpoint protection enabled, and avoid proceeding if the source is unofficial or if installation produces unexpected proxy, download, or file-modification activity.
Where this verdict could be wrong4 caveats
- The unsigned executable performed actions mapped to T1485 and T1486, techniques associated with destructive behavior, though the completed sandbox did not issue a malicious verdict.
- contactedHosts.suspiciousHosts contains www.pekora.zip; this is a cautionary reputation signal, not a confirmed malicious-host match.
- All 10 dropped children have unknown verdicts, so hasMaliciousChild=false does not establish that those files are benign.
- One communityComments entry alleges several malware categories, but it has zero votes and conflicts with both the engine results and another zero-vote clean annotation.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 engines reported a malicious or suspicious result.
- tier1Malicious=0, with 15 tier-1 engines reporting no detection.
- One completed sandbox produced no malicious verdict.
- No inspected contacted domain was known malicious.
- The file has 2,267 submissions from 1,864 sources and is 222 days old.
- The Win32 executable is unsigned and has no established signer history.
- Runtime mappings include T1485 and T1486.
- www.pekora.zip has a suspicious cached reputation score of 75.
- All 10 dropped-child verdicts remain unknown.
- File reputation is -15.
Use this hash only if it came from the expected official project channel, and keep endpoint protection enabled. Recheck the source if www.pekora.zip or the installer behavior was not expected.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 of 6 contacted hosts were cross-checked; coverage is incomplete.
YARA
CompleteRule evaluation completed with no recorded matches.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 21MITRE ATT&CK techniques
- 4spawned processes
- 16network contacts
- 36filesystem & mutex artifacts
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- setup.pekora.zip
- www.pekora.zip
- api.pekora.zip
- 172.67.144.192
- 104.21.95.120
- 8.8.8.8
- http://setup.pekora.zip/cdn.txt
- http://setup.pekora.zip/version-cde8fee1a1e747d4-ProjectXVersion.txt
- http://www.pekora.zip/install/GetInstallerCdns.ashx
- http://setup.pekora.zip/version
- http://setup.pekora.zip/version-cde8fee1a1e747d4-ProjectXApp2020L.zip
- http://setup.pekora.zip/version-cde8fee1a1e747d4-ProjectXApp2018L.zip
- HKEY_LOCAL_MACHINE\SOFTWARE\PekoraReg\(Default)
- HKEY_LOCAL_MACHINE\SOFTWARE\PekoraReg\install host
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ProxyEnable
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ProxyServer
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\SavedLegacySettings
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Pekora Corporation\Pekora\CPath
- C:\Users\<USER>\AppData\Local\Temp\KORONE-63FBE59A.log
- C:\Users\<USER>\AppData\LocalLow\rbxcsettings.rbx
- C:\Program Files (x86)\Pekora\Versions\version-cde8fee1a1e747d4\PekoraPlayerLauncher.exe
- C:\Users\<USER>\AppData\Local\Temp\KORONE-2B66D65B.tmp
- C:\Users\<USER>\AppData\Local\Temp\KORONE-A6C85783.tmp
- C:\ProgramData\Pekora\Downloads\10ed2f7e28cd563dbc7459242e38b992
- C:\ProgramData\Pekora\Downloads\3a5aa4b0c3d326bd8ff952066c2b2c0d
- C:\Program Files (x86)\Pekora\Versions\version-cde8fee1a1e747d4\2018L\AppSettings.xml
- C:\Program Files (x86)\Pekora\Versions\version-cde8fee1a1e747d4\2018L\content\avatar\character.rbxm
- C:\Program Files (x86)\Pekora\Versions\version-cde8fee1a1e747d4\2018L\content\avatar\characterR15.rbxm
- www.pekora.zip/bootstrapper
- RobloxCookieEngineMutex
- www.pekora.zip/startRobloxApp
- cversions.3.m
- \Sessions\1\BaseNamedObjects\www.pekora.zip/bootstrapper
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 6353024b909659171b5e…ed3849Never scannednever seen before
- efe4516ab96324009f74…8464e6Never scannednever seen before
- 6152344cf2210343cfac…43af33Never scannednever seen before
- 95b9f0315dd62e281944…8b576eNever scannednever seen before
- 7f9de5169ec785e73d80…147b77Never scannednever seen before
- 1ac44417987479808d45…f459bdNever scannednever seen before
- 4cf816642ab16fbb9d84…50e479Never scannednever seen before
- 793dcb17e6cad2895ada…886a56Never scannednever seen before
- adcbfdd412182977124a…5ab6efNever scannednever seen before
- ea55c33b88cbcb2109f5…271b7aNever scannednever seen before
Servers this file contacts
This file contacts 1 host we've flagged suspicious in our own URL scanner.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 75engines flagged
- 1,864sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 1,864 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 04
Scanned file: Pekora.exe — a3b3a175d5f15c7794cf51412dd54073efaa0b98376ba0b906245128f72015b3
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\Desktop\PekoraPlayerLauncher.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: KORONE-63FBE59A.log — C:\Users\<USER>\AppData\Local\Temp\KORONE-63FBE59A.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: rbxcsettings.rbx — C:\Users\<USER>\AppData\LocalLow\rbxcsettings.rbx
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: www.pekora.zip — Saved reputation verdict: suspicious.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: setup.pekora.zip — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Pekora.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 1.4 MB
- Last analyzed
- Sep 28, 2026, 4:42 PM UTC
a3b3a175d5f15c7794cf51412dd54073efaa0b98376ba0b906245128f72015b3Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Pekora.exe safe?
What is Pekora.exe?
How many antivirus engines detected Pekora.exe?
What is the SHA-256 hash of Pekora.exe?
Is it safe to run Pekora.exe?
How up to date is this analysis of Pekora.exe?
Community
Member reviews and reports for this exact file hash.