Is (unnamed file) safe?
Five high-trust engines identify trojan-like content in this new RAR archive, reinforced by defense-impairment and anti-analysis behavior during execution.
Nine of 75 engines flagged this newly observed RAR archive, including five high-trust detections naming GenKryptik, Evo, and DLL-hijacking trojan patterns. Runtime analysis also observed T1562.001 defense impairment and anti-analysis activity, although its overall sandbox label was clean and the extracted children remain unclassified.
09550fde36cdbec5b6…2b954035f39344Recommended next actions
Before opening
Do not open it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already opened 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.
Nine of 75 engines flagged this newly observed RAR archive, including five high-trust detections naming GenKryptik, Evo, and DLL-hijacking trojan patterns. Runtime analysis also observed T1562.001 defense impairment and anti-analysis activity, although its overall sandbox label was clean and the extracted children remain unclassified.
The strongest evidence is the presence of five high-trust detections among 9 of 75 engines. ESET-NOD32 names GenKryptik.HUYT, while Kaspersky identifies a generic Win64 DLL-hijacking trojan, but there is no strong single-family consensus. One completed runtime analysis observed T1562.001 defense impairment, environment detection, long sleeps, and execution from a password-protected archive. The archive is newly observed and rare, with no signer history, prior similar-file decisions, or established benign provenance. The clean sandbox label, eleven non-detecting tier-1 engines, and lack of confirmed harmful children create uncertainty, but they do not outweigh the independent high-trust detections and offensive behavior.
What We Detected
Nine of 75 antivirus engines flagged the archive, including five high-trust detections. ESET-NOD32 reported GenKryptik.HUYT, Kaspersky reported a Win64 DLL-hijacking trojan heuristic, and Avast, AVG, Avira, and F-Secure reported related Evo-style trojan detections. The family naming is not unanimous, so GenKryptik is the leading label rather than a definitive attribution.
Threat Behavior
One completed sandbox run extracted and launched an executable from a password-protected RAR archive. It observed T1562.001 defense impairment, WMI use, environment detection, long sleeps, and other anti-analysis indicators. No persistence was recorded, and the sandbox's overall label was clean. Five dropped files were inspected, but all remain unclassified, so they cannot be treated as benign.
The sample contacted multiple domains, IP addresses, and URLs. Only three hosts received a saved reputation cross-check, and one was marked suspicious; because that check did not cover every observed contact, no complete host-reputation result is available.
What To Do Now
Do not extract or execute this archive on a production system. Keep endpoint protection enabled, quarantine the file, and obtain a fresh copy only from a verified source if it is expected software. If it was already opened, run a full security scan and review the host for unexpected processes or defense-setting changes.
Where this verdict could be wrong4 caveats
- The sole completed sandbox labeled the run clean, so runtime analysis did not independently produce a malware verdict.
- Eleven tier-1 engines reported no detection, including BitDefender, Microsoft, Fortinet, and Emsisoft.
- droppedChildren.hasMaliciousChild=false, although all five child verdicts are unknown and therefore do not establish that the extracted payloads are benign.
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false provide no researcher or repository corroboration.
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 completed sandbox assigned a clean overall label
- Eleven tier-1 engines reported no detection
- No persistence indicators were recorded
- No dropped child was confirmed harmful, although all five remain unknown
- No MalwareBazaar or YARAify corroboration was found
- 9/75 antivirus detections, including five high-trust detections
- ESET-NOD32 GenKryptik.HUYT and Kaspersky DLL-hijacking trojan labels
- Observed T1562.001 defense-impairment behavior
- Anti-analysis indicators including environment detection and long sleeps
- Password-protected archive executed an extracted temporary executable
- Newly observed file with only one recorded submission
Quarantine the archive and do not open it outside an isolated analysis environment. Keep security protection enabled and perform a full system scan if the archive or its extracted executable has already run.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete9 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 of 11 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
- 9MITRE ATT&CK techniques
- 9spawned processes
- 12network contacts
- 16filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Attempted to impair or bypass security controls.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
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: Reads your Windows user-account details.
Note: Collects details about your system.
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
Scanned file
09550fde36cdbec5b660fbccf678b8d7a4e3c6816da6bda5a62b954035f39344
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\?????????????????_???????_??????????????_????_docx.z.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-6N2AT.tmp\?????????????????_???????_??????????????_????_docx.z.tmp" /SL5="$200EC,19005095,119296,C:\Users\<USER>\AppData\Local\Temp\?????????????????_???????_??????????????_????_docx.z.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
x17e6_docx.z.tmp
C:\Users\<USER>\AppData\Local\Temp\is-6N2AT.tmp\\x1794\x17d2\x179a\x1780\x17b6\x179f\x178a\x17c6\x17a1\x17be\x1784\x1790\x17d2\x1793\x17b6\x1780\x17cb_\x179a\x178a\x17d2\x178b\x1794\x17b6\x179b_\x178f\x17b6\x1798\x179c\x17c1\x1793\x1787\x17d2\x179a\x17be\x179f\x179a\x17be\x179f_\x17e2\x17e0\x17e2\x17e6_docx.z.tmp
04Isolated runtime analysis - Written fileObserved
Programs
C:\Users\user\AppData\Local\Programs
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostDerived
www.ssl.com
Saved reputation verdict: suspicious.
06Contacted-host cross-check - Contacted hostObserved
atm.teams.mira.tm.svc.cloud.microsoft
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.
- www.ssl.com
- atm.teams.mira.tm.svc.cloud.microsoft
- 1.0.0.1
- 223.5.5.5
- 223.6.6.6
- 3.222.168.199
- 9.9.9.9
- 1.1.1.1
- 142.250.69.163
- 65.75.210.175
- http://www.ssl.com/repository/SSLcom-RootCA-ECC-384-R1.crt
- http://connectivitycheck.gstatic.com/generate_204
- HKEY_CURRENT_USER\Software\Microsoft\RestartManager
- HKEY_CURRENT_USER\Software\Microsoft\RestartManager\Session0000
- C:\Users\<USER>\AppData\Local\Temp\is-6N2AT.tmp\\x1794\x17d2\x179a\x1780\x17b6\x179f\x178a\x17c6\x17a1\x17be\x1784\x1790\x17d2\x1793\x17b6\x1780\x17cb_\x179a\x178a\x17d2\x178b\x1794\x17b6\x179b_\x178f\x17b6\x1798\x179c\x17c1\x1793\x1787\x17d2\x179a\x17be\x179f\x179a\x17be\x179f_\x17e2\x17e0\x17e2\x17e6_docx.z.tmp
- C:\Users\user\AppData\Local\Programs
- C:\Users\user\AppData\Local\Programs\Common
- C:\Users\user\AppData\Local\Temp\is-0RC1V.tmp
- C:\Users\user\AppData\Local\Temp\is-0RC1V.tmp\_isetup
- \Sessions\1\BaseNamedObjects\Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- \Sessions\1\BaseNamedObjects\Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- cf0018affdd0b7921f92…4aa839Never scannednever seen before
- a7b828236be8728f9b3c…ce6cf6Never scannednever seen before
- 388a796580234efc95f3…136f95Never scannednever seen before
- 9884e9d1b4f8a873ccbd…360d87Never scannednever seen before
- 92ddd04e78fea80cb0db…b4ae9cNever 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
- 9 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
9 of 75 antivirus engines flagged the file, including Avast and AVG.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Scanned file — 09550fde36cdbec5b660fbccf678b8d7a4e3c6816da6bda5a62b954035f39344
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\AppData\Local\Temp\?????????????????_???????_??????????????_????_docx.z.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-6N2AT.tmp\?????????????????_???????_??????????????_????_docx.z.tmp" /SL5="$200EC,19005095,119296,C:\Users\<USER>\AppData\Local\Temp\?????????????????_???????_??????????????_????_docx.z.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: x17e6_docx.z.tmp — C:\Users\<USER>\AppData\Local\Temp\is-6N2AT.tmp\\x1794\x17d2\x179a\x1780\x17b6\x179f\x178a\x17c6\x17a1\x17be\x1784\x1790\x17d2\x1793\x17b6\x1780\x17cb_\x179a\x178a\x17d2\x178b\x1794\x17b6\x179b_\x178f\x17b6\x1798\x179c\x17c1\x1793\x1787\x17d2\x179a\x17be\x179f\x179a\x17be\x179f_\x17e2\x17e0\x17e2\x17e6_docx.z.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Programs — C:\Users\user\AppData\Local\Programs
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: www.ssl.com — Saved reputation verdict: suspicious.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 09
Contacted host: atm.teams.mira.tm.svc.cloud.microsoft — 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
9 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
Barely seen in the wild and first surfaced recently. 9 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- (unnamed file)
- Format
- RAR
- Code signing
- Not applicable to this file type
- Size
- 15.1 MB
- Last analyzed
- Oct 5, 2026, 4:01 AM UTC
09550fde36cdbec5b660fbccf678b8d7a4e3c6816da6bda5a62b954035f39344Safety & 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 this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already opened 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 this file malware?
What is this file?
How many antivirus engines detected this file?
I already downloaded and opened this file — what should I do?
How do I remove this file?
What kind of malware is this file?
What is the SHA-256 hash of this file?
How up to date is this analysis of this file?
Community
Member reviews and reports for this exact file hash.