Is Emulateur Valorant.zip safe?
Thirty-five of 75 engines flagged this archive, including eight tier-1 detections, while observed defense-impairment activity reinforces the trojan and game-hack labels.
The archive drew 35 detections from 75 engines, including eight tier-1 flags from vendors such as BitDefender, ESET, Sophos, and TrendMicro. Runtime observation also recorded T1562.001 defense impairment and execution of an extracted patch executable, although the single sandbox verdict was clean and network reputation coverage was incomplete.
56d544adfe0e319a8a…d2e6d8eee66cd3Recommended next actions
Before opening or extracting
Do not open or extract it. Delete this archive from the device, then empty the Recycle Bin or Trash.
If you already opened or extracted it
Close it. If it opened links, requested credentials, or triggered unexpected behavior, disconnect from the internet and run a full device scan.
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 archive drew 35 detections from 75 engines, including eight tier-1 flags from vendors such as BitDefender, ESET, Sophos, and TrendMicro. Runtime observation also recorded T1562.001 defense impairment and execution of an extracted patch executable, although the single sandbox verdict was clean and network reputation coverage was incomplete.
The detection volume is substantial: 35 of 75 engines flagged the archive, and eight independent tier-1 votes are represented. Several vendors identify the Giant family, while others report GameHack or generic trojan activity, so the precise family name varies but the harmful classification is broadly supported. Runtime observation extracted and executed Patchbyellen.exe and recorded T1560 plus T1562.001, including behavior associated with impairing defenses. The single sandbox verdict was clean, and neither external research intelligence nor the two unknown child verdicts independently confirmed the threat. Direct-IP contact was observed, but no complete host-reputation cross-check is available, so that connection is only supporting evidence.
What We Detected
Thirty-five of 75 antivirus engines flagged the ZIP archive. Eight tier-1 engines detected it, including BitDefender with Giant, ESET-NOD32 with GameHack, and TrendMicro with TEDY; other engines used generic trojan labels.
Threat Behavior
The archive extracted and launched Patchbyellen.exe. Runtime observation recorded T1560 and T1562.001, with the latter associated with impairing security defenses. It also contacted 162.159.36.2 directly, but no complete host-reputation result is available. The two extracted child hashes remain unclassified, and the single sandbox run did not issue a malware verdict.
What To Do Now
Do not open or execute the archive or its extracted patch program. Keep endpoint protection enabled, quarantine the file, and run a full system scan if it was already launched; changing game-platform credentials from a separate trusted device is also prudent.
Where this verdict could be wrong4 caveats
- behaviour.hasMaliciousSandboxVerdict=false: the single completed sandbox run returned a clean verdict.
- droppedChildren.hasMaliciousChild=false, but both extracted children have unknown verdicts rather than confirmed benign results.
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false provide no researcher-intelligence corroboration.
- engines.tier1FamilyConsensus.strong=false; only two tier-1 engines agreed on the gamehack family.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The single completed sandbox run returned a clean verdict
- No malicious dropped child was confirmed
- YARAify reported zero matching rules
- CIRCL and MalwareBazaar returned no hits
- No persistence indicators were recorded
- 35/75 antivirus detections
- Eight tier-1 malicious votes
- Multiple Giant, GameHack, and trojan labels
- T1562.001 defense-impairment activity
- Extracted Patchbyellen.exe was executed
- Direct-IP contact with incomplete reputation coverage
Quarantine and delete the archive without running its contents, and keep antivirus protection enabled. If it was executed, perform a full scan and secure associated gaming credentials from a trusted device.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete35 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 4MITRE ATT&CK techniques
- 5spawned processes
- 1network contacts
- 6filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Attempted to impair or bypass security controls.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Collects details about your system.
Note: Connected to 1 server during sandbox analysis.
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.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
Emulateur Valorant.zip
56d544adfe0e319a8abee603a145b39ee83f37a1fcabf14e93d2e6d8eee66cd3
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\SysWOW64\unarchiver.exe "C:\Windows\SysWow64\unarchiver.exe" "C:\Users\user\Desktop\Emulateur Valorant.zip"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\SysWOW64\7za.exe "C:\Windows\System32\7za.exe" x -pinfected -y -o"C:\Users\user\AppData\Local\Temp\siyu4dfb.1vr" "C:\Users\user\Desktop\Emulateur Valorant.zip"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
siyu4dfb.1vr
C:\Users\user\AppData\Local\Temp\siyu4dfb.1vr
04Isolated runtime analysis - Written fileObserved
Emulateur Valorant
C:\Users\user\AppData\Local\Temp\siyu4dfb.1vr\Emulateur Valorant
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Users\user\AppData\Local\Temp\siyu4dfb.1vr
- C:\Users\user\AppData\Local\Temp\siyu4dfb.1vr\Emulateur Valorant
- C:\Users\user\AppData\Local\Temp\siyu4dfb.1vr\Emulateur Valorant\Patchbyellen.exe
- C:\Users\user\AppData\Local\Temp\unarchiver.log
- \Device\ConDrv\\Connect
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 6c9cad4e937947fa9de9…8867a4Never scannednever seen before
- 67258f979444f49fcc3d…7af29cNever 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.
- 1rule hit recorded
- 35 / 75engines flagged
- 8sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
35 of 75 antivirus engines flagged the file, including AhnLab-V3 and ALYac.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 10 times from 8 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Emulateur Valorant.zip — 56d544adfe0e319a8abee603a145b39ee83f37a1fcabf14e93d2e6d8eee66cd3
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — C:\Windows\SysWOW64\unarchiver.exe "C:\Windows\SysWow64\unarchiver.exe" "C:\Users\user\Desktop\Emulateur Valorant.zip"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\SysWOW64\7za.exe "C:\Windows\System32\7za.exe" x -pinfected -y -o"C:\Users\user\AppData\Local\Temp\siyu4dfb.1vr" "C:\Users\user\Desktop\Emulateur Valorant.zip"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: siyu4dfb.1vr — C:\Users\user\AppData\Local\Temp\siyu4dfb.1vr
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Emulateur Valorant — C:\Users\user\AppData\Local\Temp\siyu4dfb.1vr\Emulateur Valorant
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
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.
Evidence162.159.36.2
35 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Emulateur Valorant.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 2.7 MB
- Last analyzed
- Sep 25, 2026, 8:42 PM UTC
56d544adfe0e319a8abee603a145b39ee83f37a1fcabf14e93d2e6d8eee66cd3Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't open or extract this archive. Delete this archive from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already opened or extracted it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy from the original trusted source and verify its exact hash when possible.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Emulateur Valorant.zip malware?
What is Emulateur Valorant.zip?
How many antivirus engines detected Emulateur Valorant.zip?
I already downloaded and opened or extracted Emulateur Valorant.zip — what should I do?
How do I remove Emulateur Valorant.zip?
What kind of malware is Emulateur Valorant.zip?
What is the SHA-256 hash of Emulateur Valorant.zip?
How up to date is this analysis of Emulateur Valorant.zip?
Community
Member reviews and reports for this exact file hash.