What is extract-log.exe?

extract-log.exe is usually located in the 'c:\downloads\' folder.

Some of the anti-virus scanners at VirusTotal detected extract-log.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 [?]

extract-log.exe does not have any version or vendor information.

Digital signatures [?]

extract-log.exe is not signed.

VirusTotal report

9 of the 68 anti-virus programs at VirusTotal detected the extract-log.exe file. That's a 13% detection rate.

ScannerDetection Name
AegisLab Trojan.Win32.Generic.4!c
Avira TR/Crypt.ZPACK.Gen7
CrowdStrike win/malicious_confidence_60% (W)
F-Secure Trojan.TR/Crypt.ZPACK.Gen7
Ikarus Trojan.Crypt
Jiangmin Trojan.Generic.ccprb
Qihoo-360 Win32/Trojan.af4
Rising Trojan.Crypto!8.364 (CLOUD)
Trapmine suspicious.low.ml.score
9 of the 68 anti-virus programs detected the extract-log.exe file.

Sandbox Report

The following information was gathered by executing the file inside Cuckoo Sandbox.

Summary

Successfully executed process in sandbox.

Summary

{
    "regkey_opened": [
        "HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Rpc",
        "HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows NT\\Rpc"
    ],
    "regkey_read": [
        "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Rpc\\MaxRpcSize",
        "HKEY_LOCAL_MACHINE\\SYSTEM\\Setup\\SystemSetupInProgress",
        "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\SQMClient\\Windows\\CEIPEnable",
        "HKEY_LOCAL_MACHINE\\SYSTEM\\Setup\\OOBEInProgress",
        "HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\ComputerName\\ActiveComputerName\\ComputerName"
    ],
    "dll_loaded": [
        "rpcrt4.dll"
    ]
}

Generic

[
    {
        "process_path": "C:\\Windows\\System32\\lsass.exe",
        "process_name": "lsass.exe",
        "pid": 476,
        "summary": {},
        "first_seen": 1589133185.328125,
        "ppid": 376
    },
    {
        "process_path": "C:\\Users\\cuck\\AppData\\Local\\Temp\\0b0e809e324d3c8c0f4d9b8ee3810604556744a95c6f27c1b1532ea634ce839e.bin",
        "process_name": "0b0e809e324d3c8c0f4d9b8ee3810604556744a95c6f27c1b1532ea634ce839e.bin",
        "pid": 2436,
        "summary": {
            "regkey_opened": [
                "HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Rpc",
                "HKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Windows NT\\Rpc"
            ],
            "regkey_read": [
                "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Rpc\\MaxRpcSize",
                "HKEY_LOCAL_MACHINE\\SYSTEM\\Setup\\SystemSetupInProgress",
                "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\SQMClient\\Windows\\CEIPEnable",
                "HKEY_LOCAL_MACHINE\\SYSTEM\\Setup\\OOBEInProgress",
                "HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\ComputerName\\ActiveComputerName\\ComputerName"
            ],
            "dll_loaded": [
                "rpcrt4.dll"
            ]
        },
        "first_seen": 1589133185.65625,
        "ppid": 2736
    }
]

Signatures

[
    {
        "markcount": 1,
        "families": [],
        "description": "Command line console output was observed",
        "severity": 1,
        "marks": [
            {
                "call": {
                    "category": "misc",
                    "status": 1,
                    "stacktrace": [],
                    "api": "WriteConsoleA",
                    "return_value": 1,
                    "arguments": {
                        "buffer": "Success!\r\n",
                        "console_handle": "0x00000007"
                    },
                    "time": 1589133185.78125,
                    "tid": 2124,
                    "flags": {}
                },
                "pid": 2436,
                "type": "call",
                "cid": 29
            }
        ],
        "references": [],
        "name": "console_output"
    },
    {
        "markcount": 1,
        "families": [],
        "description": "Checks amount of memory in system, this can be used to detect virtual machines that have a low amount of memory available",
        "severity": 1,
        "marks": [
            {
                "call": {
                    "category": "system",
                    "status": 1,
                    "stacktrace": [],
                    "api": "GlobalMemoryStatusEx",
                    "return_value": 1,
                    "arguments": {},
                    "time": 1589133185.74925,
                    "tid": 2124,
                    "flags": {}
                },
                "pid": 2436,
                "type": "call",
                "cid": 20
            }
        ],
        "references": [],
        "name": "antivm_memory_available"
    }
]

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": 662,
            "time": 6.116183042526245,
            "dport": 137,
            "sport": 137
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 3462,
            "time": 6.05050802230835,
            "dport": 5355,
            "sport": 51001
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 3790,
            "time": 4.125038146972656,
            "dport": 5355,
            "sport": 53595
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 4118,
            "time": 6.057892084121704,
            "dport": 5355,
            "sport": 53848
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 4446,
            "time": 4.6375720500946045,
            "dport": 5355,
            "sport": 54255
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 4774,
            "time": 2.945143938064575,
            "dport": 5355,
            "sport": 55314
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 5102,
            "time": 4.633401155471802,
            "dport": 1900,
            "sport": 1900
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 11572,
            "time": 4.146661996841431,
            "dport": 3702,
            "sport": 49152
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 15764,
            "time": 6.163210153579712,
            "dport": 1900,
            "sport": 53598
        }
    ],
    "dns_servers": [],
    "http": [],
    "icmp": [],
    "smtp": [],
    "tcp": [],
    "smtp_ex": [],
    "mitm": [],
    "hosts": [],
    "pcap_sha256": "3ded95aa807070650f16c9cf02779f7e164e07c99060fe1940f07551f482b0cd",
    "dns": [],
    "http_ex": [],
    "domains": [],
    "dead_hosts": [],
    "sorted_pcap_sha256": "402ca984c2d1b83d3f01d976131942d6e7cd9a3e80b501359456ad650b293f1c",
    "irc": [],
    "https_ex": []
}

Screenshots

Screenshot from the sandbox

extract-log.exe removal instructions

The instructions below shows how to remove extract-log.exe with help from the FreeFixer removal tool. Basically, you install FreeFixer, scan your computer, check the extract-log.exe file for removal, restart your computer and scan it again to verify that extract-log.exe has been successfully removed. Here are the removal instructions in more detail:

  1. Download and install FreeFixer: http://www.freefixer.com/download.html
  2. Start FreeFixer and press the Start Scan button. The scan will finish in approximately five minutes.
    Screenshot of Start Scan button
  3. When the scan is finished, locate extract-log.exe in the scan result and tick the checkbox next to the extract-log.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 extract-log.exe in the scan result.
    Red arrow point on the unwanted file
    c:\downloads\extract-log.exe
  4. Scroll down to the bottom of the scan result and press the Fix button. FreeFixer will now delete the extract-log.exe file.
    Screenshot of Fix button
  5. Restart your computer.
  6. Start FreeFixer and scan your computer again. If extract-log.exe still remains in the scan result, proceed with the next step. If extract-log.exe is gone from the scan result you're done.
  7. If extract-log.exe still remains in the scan result, check its checkbox again in the scan result and click Fix.
  8. Restart your computer.
  9. Start FreeFixer and scan your computer again. Verify that extract-log.exe no longer appear in the scan result.
Please select the option that best describe your thoughts on the removal instructions given above








Free Questionnaires

Hashes [?]

PropertyValue
MD53e2b9803b7449f74399eb575462889ab
SHA2560b0e809e324d3c8c0f4d9b8ee3810604556744a95c6f27c1b1532ea634ce839e

Error Messages

These are some of the error messages that can appear related to extract-log.exe:

extract-log.exe has encountered a problem and needs to close. We are sorry for the inconvenience.

extract-log.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.

extract-log.exe has stopped working.

End Program - extract-log.exe. This program is not responding.

extract-log.exe is not a valid Win32 application.

extract-log.exe - Application Error. The application failed to initialize properly (0xXXXXXXXX). Click OK to terminate the application.

What will you do with the file?

To help other users, please let us know what you will do with the file:



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.

Anthonyblony writes

0 thumbs

<a href=https://cryptolake.online/crypto3>Crypto market cap updates</a>

# 13 Mar 2025, 6:42

Leave a reply