Is rufus-4.13.exe safe?
Safe file assessment
The file has a valid code signature from Akeo Consulting.
a314db019d608e3d9b…a580080eb13b1bRecommended 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.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial5 of 13 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 signature or behavior rules matched.
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
- 14MITRE ATT&CK techniques
- 4spawned processes
- 27network contacts
- 11filesystem & mutex artifacts
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
rufus-4.13.exe
a314db019d608e3d9b2eda797ba5bbe4dfc91bcd621decd144a580080eb13b1b
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\rufus-4.13.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\rufus-4.13.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Connect
\Device\ConDrv\Connect
04Isolated runtime analysis - Written fileObserved
RufC718.tmp
C:\Users\<USER>\AppData\Local\Temp\RufC718.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
185.199.109.153
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
104.18.21.213
Contact observed during runtime.
07Isolated runtime analysis - +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.
- 185.199.109.153
- 104.18.21.213
- 140.82.114.3
- 185.199.108.133
- 140.82.112.6
- 224.0.0.251
- 224.0.0.252
- 162.159.36.2
- http://r13.c.lencr.org/79.crl
- https://rufus.ie/sbat_level.txt
- https://rufus.ie/sb_active.txt
- https://rufus.ie/sb_revoked.txt
- https://rufus.ie/Fido.ver
- https://github.com/pbatard/Fido/releases/download/v1.68/Fido.ps1.lzma
- \Device\ConDrv\Connect
- C:\Users\<USER>\AppData\Local\Temp\RufC718.tmp
- C:\Windows\System32\GroupPolicy\gpt.ini
- C:\Windows\System32\GroupPolicy\Machine\Registry.pol
- C:\Users\user\AppData\Local\Temp\Ruf973.tmp
- Global/Rufus
- \Sessions\1\BaseNamedObjects\DBWinMutex
- \Sessions\1\BaseNamedObjects\Global/Rufus
- \BaseNamedObjects\Local\SM0:5936:304:WilStaging_02
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- b6c5f5b2e2499fceb92e…92aafcNever scannednever seen before
- 14694dbee3897b6bd5aa…e8e579Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 1 / 76engines flagged
- 3,719sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The file has a valid code signature from Akeo Consulting.
ProvenanceObservedSourceCode-signing metadataObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
1 of 76 antivirus engines flagged the file, including Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: rufus-4.13.exe — a314db019d608e3d9b2eda797ba5bbe4dfc91bcd621decd144a580080eb13b1b
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\rufus-4.13.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\rufus-4.13.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Connect — \Device\ConDrv\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: RufC718.tmp — C:\Users\<USER>\AppData\Local\Temp\RufC718.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 185.199.109.153 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 104.18.21.213 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: clean
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence185.199.109.153 · 104.18.21.213 · 140.82.114.3Packed PE with sandbox-observed network activity AND engine flags. Signed packed software exists legitimately, but a signed + packed + flagged binary is a signed dropper pattern.
Evidencehttp://r13.c.lencr.org/79.crl
1 of 76 engines flagged this file
View all 76 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- rufus-4.13.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Akeo Consulting
- Size
- 1.9 MB
- Last analyzed
- Apr 24, 2026, 4:13 AM UTC
a314db019d608e3d9b2eda797ba5bbe4dfc91bcd621decd144a580080eb13b1bSafety & 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 rufus-4.13.exe safe?
What is rufus-4.13.exe?
How many antivirus engines detected rufus-4.13.exe?
Is rufus-4.13.exe digitally signed?
What is the SHA-256 hash of rufus-4.13.exe?
Is it safe to run rufus-4.13.exe?
How up to date is this analysis of rufus-4.13.exe?
Community
Member reviews and reports for this exact file hash.