Is pure.exe safe?
Two high-trust engines raise concern, but generic labels, broad prevalence, and a completed run without harmful activity leave the file’s nature unresolved.
Seven of 75 engines flagged this unsigned executable, including Symantec and TrendMicro-HouseCall, so it should not be trusted without verification. However, detections lack a strong family consensus, while one completed sandbox run showed no malicious determination, no offensive-only techniques, and only Microsoft-associated domain contacts.
694e29d55032c7f303…dc73a5a8b2868aRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
Seven of 75 engines flagged this unsigned executable, including Symantec and TrendMicro-HouseCall, so it should not be trusted without verification. However, detections lack a strong family consensus, while one completed sandbox run showed no malicious determination, no offensive-only techniques, and only Microsoft-associated domain contacts.
Seven of 75 engines detected the sample, with two independent high-trust engines contributing generic machine-learning or trojan labels. That is significant, but the engines do not strongly agree on a named family, and most high-trust products did not flag it. One completed runtime analysis recorded no malicious sandbox determination, no offensive-only techniques, no persistence, and no dropped payloads. The four observed domains were fully checked without malicious or suspicious host findings, although this does not rule out unobserved behavior. Broad distribution over more than two years and the absence of packing or high-entropy code favor a false-positive explanation. The unsigned status, anti-analysis-related tags, and two high-trust detections still justify isolating the file pending source validation.
What We Detected
Seven of 75 antivirus engines flagged the executable. Symantec reported a high-confidence machine-learning attribute and TrendMicro-HouseCall used a generic Win64 trojan label, but there is no strong agreement on a specific malware family.
Threat Behavior
One completed sandbox run produced no malicious determination and recorded no offensive-only techniques, persistence indicators, or dropped payloads. The four observed domain contacts were Microsoft-associated and all distinct contacted domains received host-reputation coverage without malicious or suspicious findings. Static inspection found no packer, no likely packing, and no high-entropy code, though debug-environment detection and long sleeps can be anti-analysis indicators.
What To Do Now
Keep endpoint protection enabled and do not run the file on a production system until its origin and expected purpose are confirmed. If execution is necessary, obtain a fresh copy from the official publisher and compare its SHA-256 or signature with the publisher's release information.
Where this verdict could be wrong4 caveats
- Symantec reported ML.Attribute.HighConfidence and TrendMicro-HouseCall reported Trojan.Win64.Gen.TL0101FK26ZI, providing two independent high-trust warning signals.
- The executable is unsigned, and file.tags includes detect-debug-environment and long-sleeps, which can indicate sandbox-evasion behavior.
- Two communityComments report generic hacktool-pattern matches, although engines.hacktoolConfirmed=false and externalIntel.yaraify.ruleCount=0.
- One community annotation alleges an unknowncheats.me contact, but that host is absent from behaviour.contactedDomains and is not corroborated by the completed runtime record.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No strong tier-1 family consensus was established.
- One completed sandbox run had no malicious determination.
- No offensive-only techniques, persistence, or dropped payloads were observed.
- All four contacted domains were covered by the host check without malicious or suspicious findings.
- The file has 898 unique sources and 1,096 submissions over more than two years.
- 7/75 antivirus engines reported a detection.
- Two independent tier-1 engines flagged the executable.
- The Win32 executable is unsigned.
- Tags indicate debug-environment detection and long sleeps.
- Community annotations contain uncorroborated generic hacktool-pattern claims.
Quarantine the file until its source and purpose are independently verified, and keep endpoint protection enabled. Prefer a signed copy obtained directly from the official publisher.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete7 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial4 of 14 contacted hosts were cross-checked; coverage is incomplete.
YARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 8MITRE ATT&CK techniques
- 5spawned processes
- 14network contacts
- 6filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Listed running processes; both legitimate software and malware may do this.
Note: Collects details about your system.
Note: Loads extra code modules while running.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
pure.exe
694e29d55032c7f303684ae4e869000a69d08551536f9a6906dc73a5a8b2868a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\694e29d55032c7f303684ae4e869000a69d08551536f9a6906dc73a5a8b2868a.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
CONOUT$
04Isolated runtime analysis - Written fileObserved
ConDrv
\Device\ConDrv
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
cdn.onenote.net
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostDerived
www.microsoft.com
Saved reputation verdict: safe.
07Contacted-host cross-check - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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.
- cdn.onenote.net
- www.microsoft.com
- res.public.onecdn.static.microsoft
- tse1.mm.bing.net
- 96.7.183.97
- 192.168.0.54
- 20.99.185.48
- 20.99.133.109
- 23.216.81.152
- 23.198.171.50
- 20.99.186.246
- 192.168.0.2
- 23.198.74.242
- 23.221.24.198
- CONOUT$
- conout$
- \Device\ConDrv
- \Device\ConDrv\\Connect
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
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
- 7 / 75engines flagged
- 898sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
7 of 75 antivirus engines flagged the file, including APEX and CrowdStrike.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 898 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 1,096 times from 898 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: pure.exe — 694e29d55032c7f303684ae4e869000a69d08551536f9a6906dc73a5a8b2868a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\694e29d55032c7f303684ae4e869000a69d08551536f9a6906dc73a5a8b2868a.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: CONOUT$
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ConDrv — \Device\ConDrv
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: cdn.onenote.net — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
7 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
- pure.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 206.5 KB
- Last analyzed
- Sep 29, 2026, 4:59 PM UTC
694e29d55032c7f303684ae4e869000a69d08551536f9a6906dc73a5a8b2868aSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is pure.exe safe, or is it malware?
What is pure.exe?
How many antivirus engines detected pure.exe?
I already downloaded and ran pure.exe — what should I do?
How do I remove pure.exe?
What is the SHA-256 hash of pure.exe?
How up to date is this analysis of pure.exe?
Community
Member reviews and reports for this exact file hash.