What is winlogs.exe?
winlogs.exe is usually located in the 'c:\downloads\' folder.
Some of the anti-virus scanners at VirusTotal detected winlogs.exe.
If you have additional information about the file, please share it with the FreeFixer users by posting a comment at the bottom of this page.
Vendor and version information [?]
The following is the available information on winlogs.exe:
| Property | Value |
|---|---|
| Internal name | hayek.exe |
| Legal copyright | Copyright (C) 2018, coroci |
| Product version | 6.1.2.6 |
| File version | 6.1.2.6 |
Here's a screenshot of the file properties when displayed by Windows Explorer:
| Internal name | hayek.exe |
| Legal copyright | Copyright (C) 2018, coroci |
| Product version | 6.1.2.6 |
| File version | 6.1.2.6 |
Digital signatures [?]
winlogs.exe is not signed.
VirusTotal report
48 of the 66 anti-virus programs at VirusTotal detected the winlogs.exe file. That's a 73% detection rate.
| Scanner | Detection Name |
|---|---|
| Ad-Aware | Trojan.GenericKD.31508050 |
| AegisLab | Trojan.Win32.Chapak.4!c |
| AhnLab-V3 | Malware/Win32.Trojanspy.C3044912 |
| Alibaba | Trojan:Any/UnSafe.a |
| ALYac | Trojan.Chapak.A |
| Antiy-AVL | Trojan/Win32.Chapak |
| Arcabit | Trojan.Generic.D1E0C652 |
| Avast | Win32:Trojan-gen |
| AVG | Win32:Trojan-gen |
| Avira | TR/Crypt.Agent.tcyvy |
| BitDefender | Trojan.GenericKD.31508050 |
| CAT-QuickHeal | Trojan.Fuerboos |
| ClamAV | Win.Packed.Gandcrab-6846115-0 |
| Comodo | TrojWare.Win32.Propagate.FA@80b9yb |
| CrowdStrike | win/malicious_confidence_90% (W) |
| Cybereason | malicious.4e01bc |
| Cyren | W32/Trojan.ZZWR-5539 |
| Emsisoft | Trojan.GenericKD.31508050 (B) |
| Endgame | malicious (high confidence) |
| ESET-NOD32 | a variant of Win32/Kryptik.GOIU |
| F-Secure | Trojan.TR/Crypt.Agent.tcyvy |
| FireEye | Generic.mg.ecf21464e01bc0ad |
| Fortinet | W32/Kryptik.GOIG!tr |
| GData | Trojan.GenericKD.31508050 |
| Ikarus | Trojan-Ransom.GandCrab |
| Jiangmin | Trojan.Chapak.arc |
| K7AntiVirus | Trojan ( 0054508f1 ) |
| K7GW | Trojan ( 0054508f1 ) |
| Kaspersky | Trojan.Win32.Chapak.bqso |
| Malwarebytes | Trojan.MalPack.GS |
| McAfee | Trojan-FPYT!ECF21464E01B |
| McAfee-GW-Edition | BehavesLike.Win32.Generic.th |
| Microsoft | Trojan:Win32/Occamy.C |
| MicroWorld-eScan | Trojan.GenericKD.31508050 |
| NANO-Antivirus | Trojan.Win32.Chapak.fngkpl |
| Paloalto | generic.ml |
| Panda | Trj/GdSda.A |
| Qihoo-360 | Win32/Trojan.305 |
| Rising | Malware.Obscure/Heur!1.A89E (CLOUD) |
| SentinelOne | DFI - Suspicious PE |
| Sophos | Mal/Generic-S |
| Tencent | Win32.Trojan.Chapak.Apmo |
| Trapmine | malicious.moderate.ml.score |
| TrendMicro-HouseCall | TrojanSpy.Win32.FAREIT.SMKC.hp |
| VBA32 | BScope.Trojan.Chapak |
| Yandex | Trojan.Chapak! |
| Zillya | Trojan.Chapak.Win32.57848 |
| ZoneAlarm | Trojan.Win32.Chapak.bqso |
Sandbox Report
The following information was gathered by executing the file inside Cuckoo Sandbox.
Summary
Successfully executed process in sandbox.
Summary
{
"regkey_read": [
"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\GRE_Initialize\\DisableMetaFiles"
],
"dll_loaded": [
"kernel32.dll"
]
}Generic
[
{
"process_path": "C:\\Users\\cuck\\AppData\\Local\\Temp\\5dccce9b5611781c0edee4fae015119b49ce9eb99ee779e161ec0e75c1c383da.bin",
"process_name": "5dccce9b5611781c0edee4fae015119b49ce9eb99ee779e161ec0e75c1c383da.bin",
"pid": 2740,
"summary": {
"regkey_read": [
"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\GRE_Initialize\\DisableMetaFiles"
],
"dll_loaded": [
"kernel32.dll"
]
},
"first_seen": 1582361584.578125,
"ppid": 2780
},
{
"process_path": "C:\\Windows\\System32\\lsass.exe",
"process_name": "lsass.exe",
"pid": 476,
"summary": {},
"first_seen": 1582361584.34375,
"ppid": 376
}
]Signatures
[
{
"markcount": 1,
"families": [],
"description": "The executable contains unknown PE section names indicative of a packer (could be a false positive)",
"severity": 1,
"marks": [
{
"category": "section",
"ioc": ".mysec10",
"type": "ioc",
"description": null
}
],
"references": [],
"name": "pe_features"
},
{
"markcount": 3,
"families": [],
"description": "The file contains an unknown PE resource name possibly indicative of a packer",
"severity": 1,
"marks": [
{
"category": "resource name",
"ioc": "TIXAHAWERALUZUJICEHOWODIZO",
"type": "ioc",
"description": null
},
{
"category": "resource name",
"ioc": "WAHULEPOKIKUWUCETUMAGI",
"type": "ioc",
"description": null
},
{
"category": "resource name",
"ioc": "None",
"type": "ioc",
"description": null
}
],
"references": [],
"name": "pe_unknown_resource_name"
},
{
"markcount": 1,
"families": [],
"description": "Allocates read-write-execute memory (usually to unpack itself)",
"severity": 2,
"marks": [
{
"call": {
"category": "process",
"status": 1,
"stacktrace": [],
"api": "NtProtectVirtualMemory",
"return_value": 0,
"arguments": {
"process_identifier": 2740,
"stack_dep_bypass": 0,
"stack_pivoted": 0,
"heap_dep_bypass": 1,
"length": 905216,
"protection": 64,
"process_handle": "0xffffffff",
"base_address": "0x01ed0000"
},
"time": 1582361614.515125,
"tid": 2436,
"flags": {
"protection": "PAGE_EXECUTE_READWRITE"
}
},
"pid": 2740,
"type": "call",
"cid": 811627
}
],
"references": [],
"name": "allocates_rwx"
},
{
"markcount": 7,
"families": [],
"description": "Foreign language identified in PE resource",
"severity": 2,
"marks": [
{
"name": "TIXAHAWERALUZUJICEHOWODIZO",
"language": "LANG_SERBIAN",
"offset": "0x001692b4",
"filetype": "ASCII text, with no line terminators",
"sublanguage": "SUBLANG_DEFAULT",
"type": "generic",
"size": "0x00000070"
},
{
"name": "WAHULEPOKIKUWUCETUMAGI",
"language": "LANG_SERBIAN",
"offset": "0x00169324",
"filetype": "ASCII text, with no line terminators",
"sublanguage": "SUBLANG_DEFAULT",
"type": "generic",
"size": "0x00000100"
},
{
"name": "RT_ICON",
"language": "LANG_SERBIAN",
"offset": "0x00169424",
"filetype": "dBase IV DBT of @.DBF, block length 4096, next free block index 40, next free block 0, next used block 0",
"sublanguage": "SUBLANG_DEFAULT",
"type": "generic",
"size": "0x000010a8"
},
{
"name": "RT_STRING",
"language": "LANG_SERBIAN",
"offset": "0x0016a4cc",
"filetype": "data",
"sublanguage": "SUBLANG_DEFAULT",
"type": "generic",
"size": "0x000003a0"
},
{
"name": "RT_GROUP_ICON",
"language": "LANG_SERBIAN",
"offset": "0x0016a86c",
"filetype": "MS Windows icon resource - 1 icon, 32x32",
"sublanguage": "SUBLANG_DEFAULT",
"type": "generic",
"size": "0x00000014"
},
{
"name": "RT_VERSION",
"language": "LANG_SERBIAN",
"offset": "0x0016a880",
"filetype": "data",
"sublanguage": "SUBLANG_DEFAULT",
"type": "generic",
"size": "0x000001d0"
},
{
"name": "None",
"language": "LANG_SERBIAN",
"offset": "0x0016ae70",
"filetype": "data",
"sublanguage": "SUBLANG_DEFAULT",
"type": "generic",
"size": "0x0000000a"
}
],
"references": [],
"name": "origin_langid"
},
{
"markcount": 1,
"families": [],
"description": "Looks for the Windows Idle Time to determine the uptime",
"severity": 3,
"marks": [
{
"call": {
"category": "system",
"status": 1,
"stacktrace": [],
"api": "NtQuerySystemInformation",
"return_value": 0,
"arguments": {
"information_class": 8
},
"time": 1582361584.703125,
"tid": 2436,
"flags": {
"information_class": "SystemProcessorPerformanceInformation"
}
},
"pid": 2740,
"type": "call",
"cid": 19
}
],
"references": [],
"name": "antisandbox_idletime"
}
]Yara
The Yara rules did not detect anything in the file.
Network
{
"tls": [],
"udp": [
{
"src": "192.168.56.101",
"dst": "192.168.56.255",
"offset": 546,
"time": 3.0789570808410645,
"dport": 137,
"sport": 137
},
{
"src": "192.168.56.101",
"dst": "192.168.56.255",
"offset": 5226,
"time": 9.078171014785767,
"dport": 138,
"sport": 138
},
{
"src": "192.168.56.101",
"dst": "224.0.0.252",
"offset": 7070,
"time": 3.0426011085510254,
"dport": 5355,
"sport": 51001
},
{
"src": "192.168.56.101",
"dst": "224.0.0.252",
"offset": 7398,
"time": 1.033452033996582,
"dport": 5355,
"sport": 53595
},
{
"src": "192.168.56.101",
"dst": "224.0.0.252",
"offset": 7726,
"time": 3.0662171840667725,
"dport": 5355,
"sport": 53848
},
{
"src": "192.168.56.101",
"dst": "224.0.0.252",
"offset": 8054,
"time": 1.5352721214294434,
"dport": 5355,
"sport": 54255
},
{
"src": "192.168.56.101",
"dst": "224.0.0.252",
"offset": 8382,
"time": -0.0921628475189209,
"dport": 5355,
"sport": 55314
},
{
"src": "192.168.56.101",
"dst": "239.255.255.250",
"offset": 8710,
"time": 1.6409180164337158,
"dport": 1900,
"sport": 1900
},
{
"src": "192.168.56.101",
"dst": "239.255.255.250",
"offset": 28120,
"time": 1.0667061805725098,
"dport": 3702,
"sport": 49152
},
{
"src": "192.168.56.101",
"dst": "239.255.255.250",
"offset": 36504,
"time": 3.1505839824676514,
"dport": 1900,
"sport": 53598
}
],
"dns_servers": [],
"http": [],
"icmp": [],
"smtp": [],
"tcp": [],
"smtp_ex": [],
"mitm": [],
"hosts": [],
"pcap_sha256": "47c31c18218a2c9174bc9d99e041c86cde7133a823e7ffdeaefeb5f32ff3dea5",
"dns": [],
"http_ex": [],
"domains": [],
"dead_hosts": [],
"sorted_pcap_sha256": "1d97e674d9066909ef23b9fd132093b5b1a98c2d842ac8fcc10f7840fa05bec8",
"irc": [],
"https_ex": []
}Screenshots
winlogs.exe removal instructions
The instructions below shows how to remove winlogs.exe with help from the FreeFixer removal tool. Basically, you install FreeFixer, scan your computer, check the winlogs.exe file for removal, restart your computer and scan it again to verify that winlogs.exe has been successfully removed. Here are the removal instructions in more detail:
- Download and install FreeFixer: http://www.freefixer.com/download.html
- Start FreeFixer and press the Start Scan button. The scan will finish in approximately five minutes.
- When the scan is finished, locate winlogs.exe in the scan result and tick the checkbox next to the winlogs.exe file. Do not check any other file for removal unless you are 100% sure you want to delete it. Tip: Press CTRL-F to open up FreeFixer's search dialog to quickly locate winlogs.exe in the scan result.
c:\downloads\winlogs.exe 
- Scroll down to the bottom of the scan result and press the Fix button. FreeFixer will now delete the winlogs.exe file.
- Restart your computer.
- Start FreeFixer and scan your computer again. If winlogs.exe still remains in the scan result, proceed with the next step. If winlogs.exe is gone from the scan result you're done.
- If winlogs.exe still remains in the scan result, check its checkbox again in the scan result and click Fix.
- Restart your computer.
- Start FreeFixer and scan your computer again. Verify that winlogs.exe no longer appear in the scan result.
Hashes [?]
| Property | Value |
|---|---|
| MD5 | ecf21464e01bc0ade28b16256300c916 |
| SHA256 | 5dccce9b5611781c0edee4fae015119b49ce9eb99ee779e161ec0e75c1c383da |
Error Messages
These are some of the error messages that can appear related to winlogs.exe:
winlogs.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
winlogs.exe - Application Error. The instruction at "0xXXXXXXXX" referenced memory at "0xXXXXXXXX". The memory could not be "read/written". Click on OK to terminate the program.
winlogs.exe has stopped working.
End Program - winlogs.exe. This program is not responding.
winlogs.exe is not a valid Win32 application.
winlogs.exe - Application Error. The application failed to initialize properly (0xXXXXXXXX). Click OK to terminate the application.
What will you do with winlogs.exe?
To help other users, please let us know what you will do with winlogs.exe:
Comments
Please share with the other users what you think about this file. What does this file do? Is it legitimate or something that your computer is better without? Do you know how it was installed on your system? Did you install it yourself or did it come bundled with some other software? Is it running smoothly or do you get some error message? Any information that will help to document this file is welcome. Thank you for your contributions.
I'm reading all new comments so don't hesitate to post a question about the file. If I don't have the answer perhaps another user can help you.
No comments posted yet.