What is injclient.exe?

injclient.exe is part of skr and developed by Cool Moon according to the injclient.exe version information.

injclient.exe's description is "Moon Sky"

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

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

VirusTotal report

38 of the 64 anti-virus programs at VirusTotal detected the injclient.exe file. That's a 59% detection rate.

Scanner	Detection Name
Acronis	suspicious
Ad-Aware	Trojan.GenericKD.31740667
AhnLab-V3	Malware/Win32.Generic.C3058190
ALYac	Trojan.GenericKD.31740667
Antiy-AVL	Trojan[Spy]/Win32.Noon
Arcabit	Trojan.Generic.D1E452FB
Avira	TR/Crypt.ZPACK.Gen2
BitDefender	Trojan.GenericKD.31740667
CrowdStrike	win/malicious_confidence_90% (W)
Cybereason	malicious.812267
Cyren	W32/GenBl.865E9897!Olympus
DrWeb	Trojan.Fbng.8
Emsisoft	Trojan.GenericKD.31740667 (B)
Endgame	malicious (high confidence)
ESET-NOD32	a variant of Win32/GenKryptik.DBEH
F-Secure	Trojan.TR/Crypt.ZPACK.Gen2
Fortinet	W32/GenKryptik.DBEH!tr
GData	Win32.Trojan-Stealer.FormBook.DBK8IX
Ikarus	Trojan.Win32.Bublik
K7AntiVirus	Trojan ( 00548f8f1 )
K7GW	Trojan ( 00548f8f1 )
Kaspersky	Trojan-Spy.Win32.Noon.aawn
Malwarebytes	Trojan.Injector
McAfee	RDN/Generic.dx
McAfee-GW-Edition	BehavesLike.Win32.ICLoader.dc
Microsoft	Trojan:Win32/Tiggre!plock
MicroWorld-eScan	Trojan.GenericKD.31740667
Paloalto	generic.ml
Panda	Trj/GdSda.A
Qihoo-360	Trojan.Generic
SentinelOne	static engine - malicious
Sophos	Mal/Generic-S
Symantec	Trojan.Gen.2
Tencent	Win32.Trojan-spy.Noon.Dztu
Trapmine	malicious.high.ml.score
VBA32	BScope.Trojan.Occamy
VIPRE	Trojan.Win32.Generic!BT
ZoneAlarm	Trojan-Spy.Win32.Noon.aawn

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"
    ]
}

Generic

[
    {
        "process_path": "C:\\Users\\cuck\\AppData\\Local\\Temp\\1827888204e1a409b6fba098aed9ab8fa8ef529efaa7e8608a303c0f9a10c7c5.bin",
        "process_name": "1827888204e1a409b6fba098aed9ab8fa8ef529efaa7e8608a303c0f9a10c7c5.bin",
        "pid": 2420,
        "summary": {
            "regkey_read": [
                "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\GRE_Initialize\\DisableMetaFiles"
            ]
        },
        "first_seen": 1602438788.59375,
        "ppid": 1268
    },
    {
        "process_path": "C:\\Windows\\System32\\lsass.exe",
        "process_name": "lsass.exe",
        "pid": 476,
        "summary": {},
        "first_seen": 1602438788.34375,
        "ppid": 376
    }
]

Signatures

[
    {
        "markcount": 1,
        "families": [],
        "description": "The executable uses a known packer",
        "severity": 1,
        "marks": [
            {
                "category": "packer",
                "ioc": "Armadillo v1.71",
                "type": "ioc",
                "description": null
            }
        ],
        "references": [],
        "name": "peid_packer"
    },
    {
        "markcount": 1,
        "families": [],
        "description": "One or more processes crashed",
        "severity": 1,
        "marks": [
            {
                "call": {
                    "category": "__notification__",
                    "status": 1,
                    "stacktrace": [],
                    "raw": [
                        "stacktrace"
                    ],
                    "api": "__exception__",
                    "return_value": 0,
                    "arguments": {
                        "stacktrace": "B\na\ns\ne\nT\nh\nr\ne\na\nd\nI\nn\ni\nt\nT\nh\nu\nn\nk\n+\n0\nx\n1\n2\n \nV\ne\nr\ni\nf\ny\nC\no\nn\ns\no\nl\ne\nI\no\nH\na\nn\nd\nl\ne\n-\n0\nx\nb\n3\n \nk\ne\nr\nn\ne\nl\n3\n2\n+\n0\nx\n1\n3\n3\nc\na\n \n@\n \n0\nx\n7\n5\nb\nc\n3\n3\nc\na\n\n\nR\nt\nl\nI\nn\ni\nt\ni\na\nl\ni\nz\ne\nE\nx\nc\ne\np\nt\ni\no\nn\nC\nh\na\ni\nn\n+\n0\nx\n6\n3\n \nR\nt\nl\nA\nl\nl\no\nc\na\nt\ne\nA\nc\nt\ni\nv\na\nt\ni\no\nn\nC\no\nn\nt\ne\nx\nt\nS\nt\na\nc\nk\n-\n0\nx\na\n1\n \nn\nt\nd\nl\nl\n+\n0\nx\n3\n9\ne\nd\n2\n \n@\n \n0\nx\n7\n7\nb\nc\n9\ne\nd\n2\n\n\nR\nt\nl\nI\nn\ni\nt\ni\na\nl\ni\nz\ne\nE\nx\nc\ne\np\nt\ni\no\nn\nC\nh\na\ni\nn\n+\n0\nx\n3\n6\n \nR\nt\nl\nA\nl\nl\no\nc\na\nt\ne\nA\nc\nt\ni\nv\na\nt\ni\no\nn\nC\no\nn\nt\ne\nx\nt\nS\nt\na\nc\nk\n-\n0\nx\nc\ne\n \nn\nt\nd\nl\nl\n+\n0\nx\n3\n9\ne\na\n5\n \n@\n \n0\nx\n7\n7\nb\nc\n9\ne\na\n5",
                        "registers": {
                            "esp": 1638044,
                            "edi": 1983568635,
                            "eax": 4387192,
                            "ebp": 1638280,
                            "edx": 2130566132,
                            "ebx": 4194304,
                            "esi": 65688,
                            "ecx": 3341942784
                        },
                        "exception": {
                            "instruction_r": "ff ee ff ee 00 00 00 00 00 00 10 00 00 00 00 00",
                            "exception_code": "0xc000001d",
                            "symbol": "",
                            "address": "0x100a0"
                        }
                    },
                    "time": 1602438794.09375,
                    "tid": 2460,
                    "flags": {}
                },
                "pid": 2420,
                "type": "call",
                "cid": 10
            }
        ],
        "references": [],
        "name": "raises_exception"
    },
    {
        "markcount": 2,
        "families": [],
        "description": "The binary likely contains encrypted or compressed data indicative of a packer",
        "severity": 2,
        "marks": [
            {
                "entropy": 7.647633576407848,
                "section": {
                    "size_of_data": "0x0002b000",
                    "virtual_address": "0x00005000",
                    "entropy": 7.647633576407848,
                    "name": ".data",
                    "virtual_size": "0x0002ab5c"
                },
                "type": "generic",
                "description": "A section with a high entropy has been found"
            },
            {
                "entropy": 0.7962962962962963,
                "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.1114721298217773,
            "dport": 137,
            "sport": 137
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 6082,
            "time": 3.0191919803619385,
            "dport": 5355,
            "sport": 51001
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 6410,
            "time": 1.0151140689849854,
            "dport": 5355,
            "sport": 53595
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 6738,
            "time": 3.063631057739258,
            "dport": 5355,
            "sport": 53848
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7066,
            "time": 1.5190720558166504,
            "dport": 5355,
            "sport": 54255
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7394,
            "time": -0.10074090957641602,
            "dport": 5355,
            "sport": 55314
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 7722,
            "time": 1.0359001159667969,
            "dport": 1900,
            "sport": 1900
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 26040,
            "time": 1.0361700057983398,
            "dport": 3702,
            "sport": 49152
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 34424,
            "time": 3.1257071495056152,
            "dport": 1900,
            "sport": 53598
        }
    ],
    "dns_servers": [],
    "http": [],
    "icmp": [],
    "smtp": [],
    "tcp": [],
    "smtp_ex": [],
    "mitm": [],
    "hosts": [],
    "pcap_sha256": "6d6b5672a0ce9c2b5d3d4e9bf9fae6ddaf2599f40890362cb7fcbb7fc09f28d4",
    "dns": [],
    "http_ex": [],
    "domains": [],
    "dead_hosts": [],
    "sorted_pcap_sha256": "d50fe954158bbb50b83b58ad2088df2791bedd2db9efd09d6490bdadeafe49e1",
    "irc": [],
    "https_ex": []
}

Screenshots

injclient.exe removal instructions

The instructions below shows how to remove injclient.exe with help from the FreeFixer removal tool. Basically, you install FreeFixer, scan your computer, check the injclient.exe file for removal, restart your computer and scan it again to verify that injclient.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.

   
3. When the scan is finished, locate injclient.exe in the scan result and tick the checkbox next to the injclient.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 injclient.exe in the scan result.

   

   

   c:\downloads\injclient.exe

   
4. Scroll down to the bottom of the scan result and press the Fix button. FreeFixer will now delete the injclient.exe file.

   
5. Restart your computer.
6. Start FreeFixer and scan your computer again. If injclient.exe still remains in the scan result, proceed with the next step. If injclient.exe is gone from the scan result you're done.
7. If injclient.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 injclient.exe no longer appear in the scan result.

Error Messages

• Privacy Policy