What is cl.exe?

cl.exe is part of EpicNet Cloud Office and developed by EpicNet Inc. according to the cl.exe version information.

cl.exe's description is "Cloud Net"

cl.exe is usually located in the 'c:\downloads\' folder.

Some of the anti-virus scanners at VirusTotal detected cl.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 cl.exe:

PropertyValue
Product nameEpicNet Cloud Office
Company nameEpicNet Inc.
File descriptionCloud Net
Internal namecloudnet.exe
Original filenamecloudnet.exe
Legal copyrightCopyright © 2017
Product version7.2.1.1
File version7.2.1.1

Here's a screenshot of the file properties when displayed by Windows Explorer:

Product nameEpicNet Cloud Office
Company nameEpicNet Inc.
File descriptionCloud Net
Internal namecloudnet.exe
Original filenamecloudnet.exe
Legal copyrightCopyright © 2017
Product version7.2.1.1
File version7.2.1.1

Digital signatures [?]

cl.exe is not signed.

VirusTotal report

56 of the 71 anti-virus programs at VirusTotal detected the cl.exe file. That's a 79% detection rate.

ScannerDetection Name
Acronis suspicious
Ad-Aware Gen:Variant.Razy.348484
AegisLab Trojan.Win32.Glupteba.4!c
AhnLab-V3 Trojan/Win32.SmearPasse.R247805
Alibaba TrojanProxy:Win32/Glupteba.91c27fda
ALYac Gen:Variant.Razy.348484
Antiy-AVL Trojan[Proxy]/Win32.Glupteba
Arcabit Trojan.Razy.D55144
Avast Win32:CrypterX-gen [Trj]
AVG Win32:CrypterX-gen [Trj]
Avira TR/Crypt.XPACK.Gen2
BitDefender Gen:Variant.Razy.348484
Bkav W32.KillProcSMB.Worm
CAT-QuickHeal Trojan.Glupteba.S5486226
Comodo TrojWare.Win32.Glupteba.BC@82zlxv
CrowdStrike win/malicious_confidence_90% (W)
Cybereason malicious.d06c81
Cylance Unsafe
Cyren W32/Glupteba.A.gen!Eldorado
DrWeb Trojan.Proxy2.1436
Emsisoft Gen:Variant.Razy.348484 (B)
Endgame malicious (high confidence)
ESET-NOD32 a variant of Win32/Glupteba.BC
F-Prot W32/Glupteba.A.gen!Eldorado
F-Secure Trojan.TR/Crypt.XPACK.Gen2
FireEye Generic.mg.5fb695cd06c81fb7
Fortinet W32/Generic.AP.128842!tr
GData Gen:Variant.Razy.348484
Ikarus Trojan.Win32.Glupteba
Invincea heuristic
Jiangmin TrojanProxy.Glupteba.adt
K7AntiVirus Trojan ( 005115a11 )
K7GW Trojan ( 005115a11 )
Kaspersky HEUR:Trojan-Proxy.Win32.Glupteba.gen
Malwarebytes Trojan.BitCoinMiner
MAX malware (ai score=100)
McAfee Trojan-FQGO!5FB695CD06C8
McAfee-GW-Edition BehavesLike.Win32.Generic.jc
Microsoft Trojan:Win32/Glupteba
MicroWorld-eScan Gen:Variant.Razy.348484
NANO-Antivirus Trojan.Win32.Glupteba.fpthou
Paloalto generic.ml
Panda Trj/Genetic.gen
Qihoo-360 Win32/Trojan.Proxy.6bb
Rising Trojan.Proxy-Glupteba!8.307D (CLOUD)
SentinelOne DFI - Malicious PE
Sophos Troj/Glupteba-M
SUPERAntiSpyware Hack.Tool/Gen-BitCoinMiner
Symantec Trojan.Gen.MBT
Tencent Win32.Trojan-proxy.Glupteba.Tapi
Trapmine malicious.high.ml.score
TrendMicro-HouseCall TROJ_GEN.R002C0DE319
VIPRE Trojan.Win32.Generic!BT
ViRobot Trojan.Win32.Z.Glupteba.683008.JNR
Webroot W32.Trojan.Gen
ZoneAlarm HEUR:Trojan-Proxy.Win32.Glupteba.gen
56 of the 71 anti-virus programs detected the cl.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_CURRENT_USER\\SOFTWARE\\Microsoft\\TestApp"
    ],
    "mutex": [
        "Global\\Mp6c3Ygukx29GbDk",
        "Global\\5afa3c562f5bf2eff62de390e531c25d",
        "Global\\22b91e866a98674f898cc7add8841a39"
    ],
    "regkey_read": [
        "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\GRE_Initialize\\DisableMetaFiles"
    ],
    "dll_loaded": [
        "kernel32"
    ]
}

Generic

[
    {
        "process_path": "C:\\Users\\cuck\\AppData\\Local\\Temp\\637eb002a9e603f00ac38f76967cf922e58580d8cc5a50d62a67cf5d97b80a13.bin",
        "process_name": "637eb002a9e603f00ac38f76967cf922e58580d8cc5a50d62a67cf5d97b80a13.bin",
        "pid": 2740,
        "summary": {
            "regkey_opened": [
                "HKEY_CURRENT_USER\\SOFTWARE\\Microsoft\\TestApp"
            ],
            "mutex": [
                "Global\\Mp6c3Ygukx29GbDk",
                "Global\\5afa3c562f5bf2eff62de390e531c25d",
                "Global\\22b91e866a98674f898cc7add8841a39"
            ],
            "regkey_read": [
                "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\GRE_Initialize\\DisableMetaFiles"
            ],
            "dll_loaded": [
                "kernel32"
            ]
        },
        "first_seen": 1568764390.6406,
        "ppid": 1664
    },
    {
        "process_path": "C:\\Windows\\System32\\lsass.exe",
        "process_name": "lsass.exe",
        "pid": 476,
        "summary": {},
        "first_seen": 1568764390.3438,
        "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": "init",
                "type": "ioc",
                "description": null
            }
        ],
        "references": [],
        "name": "pe_features"
    },
    {
        "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": 0,
                        "length": 524288,
                        "protection": 64,
                        "process_handle": "0xffffffff",
                        "base_address": "0x00401000"
                    },
                    "time": 1568764390.7346,
                    "tid": 2436,
                    "flags": {
                        "protection": "PAGE_EXECUTE_READWRITE"
                    }
                },
                "pid": 2740,
                "type": "call",
                "cid": 0
            }
        ],
        "references": [],
        "name": "allocates_rwx"
    },
    {
        "markcount": 2,
        "families": [],
        "description": "The binary likely contains encrypted or compressed data indicative of a packer",
        "severity": 2,
        "marks": [
            {
                "entropy": 7.7952099653104,
                "section": {
                    "size_of_data": "0x0007f600",
                    "virtual_address": "0x00001000",
                    "entropy": 7.7952099653104,
                    "name": ".text",
                    "virtual_size": "0x0007f465"
                },
                "type": "generic",
                "description": "A section with a high entropy has been found"
            },
            {
                "entropy": 0.76501501501502,
                "type": "generic",
                "description": "Overall entropy of this PE file is high"
            }
        ],
        "references": [
            "http:\/\/www.forensickb.com\/2013\/03\/file-entropy-explained.html",
            "http:\/\/virii.es\/U\/Using%20Entropy%20Analysis%20to%20Find%20Encrypted%20and%20Packed%20Malware.pdf"
        ],
        "name": "packer_entropy"
    }
]

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.0783848762512,
            "dport": 137,
            "sport": 137
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 2018,
            "time": 3.0358610153198,
            "dport": 5355,
            "sport": 51001
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 2346,
            "time": 1.0155639648438,
            "dport": 5355,
            "sport": 53595
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 2674,
            "time": 3.0473589897156,
            "dport": 5355,
            "sport": 53848
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 3002,
            "time": 1.5204758644104,
            "dport": 5355,
            "sport": 54255
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 3330,
            "time": -0.10251712799072,
            "dport": 5355,
            "sport": 55314
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 3658,
            "time": 1.5311100482941,
            "dport": 1900,
            "sport": 1900
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 6986,
            "time": 1.0481128692627,
            "dport": 3702,
            "sport": 49152
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 11178,
            "time": 3.1095149517059,
            "dport": 1900,
            "sport": 53598
        }
    ],
    "dns_servers": [],
    "http": [],
    "icmp": [],
    "smtp": [],
    "tcp": [],
    "smtp_ex": [],
    "mitm": [],
    "hosts": [],
    "pcap_sha256": "82be26e0d26879edc009c2c9f67ce2fcbab85771f47c4d58efc553035b124be1",
    "dns": [],
    "http_ex": [],
    "domains": [],
    "dead_hosts": [],
    "sorted_pcap_sha256": "cc4596234490e7d3d8b69b56476a31162bc942fbececd50bcc46515f5650b120",
    "irc": [],
    "https_ex": []
}

Screenshots

Screenshot from the sandbox

cl.exe removal instructions

The instructions below shows how to remove cl.exe with help from the FreeFixer removal tool. Basically, you install FreeFixer, scan your computer, check the cl.exe file for removal, restart your computer and scan it again to verify that cl.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 cl.exe in the scan result and tick the checkbox next to the cl.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 cl.exe in the scan result.
    Red arrow point on the unwanted file
    c:\downloads\cl.exe
  4. Scroll down to the bottom of the scan result and press the Fix button. FreeFixer will now delete the cl.exe file.
    Screenshot of Fix button
  5. Restart your computer.
  6. Start FreeFixer and scan your computer again. If cl.exe still remains in the scan result, proceed with the next step. If cl.exe is gone from the scan result you're done.
  7. If cl.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 cl.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
MD55fb695cd06c81fb7a32b7df7e069b5b6
SHA256637eb002a9e603f00ac38f76967cf922e58580d8cc5a50d62a67cf5d97b80a13

Error Messages

These are some of the error messages that can appear related to cl.exe:

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

cl.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.

Cloud Net has stopped working.

End Program - cl.exe. This program is not responding.

cl.exe is not a valid Win32 application.

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

What will you do with cl.exe?

To help other users, please let us know what you will do with cl.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.

Leave a reply