What is jsmk2202.exe?

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

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

jsmk2202.exe does not have any version or vendor information.

Digital signatures [?]

jsmk2202.exe is not signed.

VirusTotal report

42 of the 62 anti-virus programs at VirusTotal detected the jsmk2202.exe file. That's a 68% detection rate.

ScannerDetection Name
Acronis suspicious
Ad-Aware Trojan.GenericKD.41029773
Antiy-AVL Trojan[Downloader]/Win32.Dofoil
Arcabit Trojan.Generic.D272108D
Avast Win32:Trojan-gen
AVG Win32:Trojan-gen
Avira TR/Kryptik.gsijs
BitDefender Trojan.GenericKD.41029773
Comodo Malware@#tytgqkbk8iku
CrowdStrike win/malicious_confidence_90% (W)
Cyren W32/GenBl.D3EE8337!Olympus
Emsisoft Trojan.GenericKD.41029773 (B)
Endgame malicious (high confidence)
ESET-NOD32 a variant of Win32/Kryptik.GPYU
F-Secure Trojan.TR/Kryptik.gsijs
Fortinet W32/Kryptik.CXZP!tr
GData Trojan.GenericKD.41029773
Ikarus Trojan.Win32.Krypt
Invincea heuristic
Jiangmin TrojanDownloader.Dofoil.bqg
K7AntiVirus Trojan ( 00547c961 )
K7GW Trojan ( 00547c961 )
Kaspersky Trojan-Downloader.Win32.Dofoil.bwzg
Malwarebytes Trojan.Crypt
McAfee RDN/Generic.dx
McAfee-GW-Edition BehavesLike.Win32.Dropper.dh
Microsoft Trojan:Win32/Skeeyah.A!bit
MicroWorld-eScan Trojan.GenericKD.41029773
NANO-Antivirus Trojan.Win32.Dofoil.fnfuxg
Paloalto generic.ml
Panda Trj/GdSda.A
Qihoo-360 Win32/Trojan.Downloader.35b
SentinelOne static engine - malicious
Sophos Troj/Inject-DWU
Symantec Trojan.Gen.2
Tencent Win32.Trojan.Inject.Auto
Trapmine malicious.moderate.ml.score
VBA32 BScope.Trojan.Inject
VIPRE LooksLike.Win32.Crowti.b (v)
Webroot W32.Trojan.Gen
Yandex Trojan.DL.Dofoil!iGru5SzXLt0
ZoneAlarm Trojan-Downloader.Win32.Dofoil.bwzg
42 of the 62 anti-virus programs detected the jsmk2202.exe file.

Sandbox Report

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

Summary

Successfully executed process in sandbox.

Summary

{
    "command_line": [
        "C:\\Users\\cuck\\AppData\\Local\\Temp\\849d1cb5da2a0498761545156aff746e8e6f41f85f48358357b3d6aaf9085a70.bin"
    ]
}

Generic

[
    {
        "process_path": "C:\\Users\\cuck\\AppData\\Local\\Temp\\849d1cb5da2a0498761545156aff746e8e6f41f85f48358357b3d6aaf9085a70.bin",
        "process_name": "849d1cb5da2a0498761545156aff746e8e6f41f85f48358357b3d6aaf9085a70.bin",
        "pid": 1512,
        "summary": {
            "command_line": [
                "C:\\Users\\cuck\\AppData\\Local\\Temp\\849d1cb5da2a0498761545156aff746e8e6f41f85f48358357b3d6aaf9085a70.bin"
            ]
        },
        "first_seen": 1603792386.546875,
        "ppid": 2892
    },
    {
        "process_path": "C:\\Users\\cuck\\AppData\\Local\\Temp\\849d1cb5da2a0498761545156aff746e8e6f41f85f48358357b3d6aaf9085a70.bin",
        "process_name": "849d1cb5da2a0498761545156aff746e8e6f41f85f48358357b3d6aaf9085a70.bin",
        "pid": 1516,
        "summary": {},
        "first_seen": 1603792392.937124,
        "ppid": 1512
    },
    {
        "process_path": "C:\\Windows\\System32\\lsass.exe",
        "process_name": "lsass.exe",
        "pid": 476,
        "summary": {},
        "first_seen": 1603792386.296875,
        "ppid": 376
    }
]

Signatures

[
    {
        "markcount": 2,
        "families": [],
        "description": "The executable contains unknown PE section names indicative of a packer (could be a false positive)",
        "severity": 1,
        "marks": [
            {
                "category": "section",
                "ioc": ".kindata",
                "type": "ioc",
                "description": null
            },
            {
                "category": "section",
                "ioc": ".bigup",
                "type": "ioc",
                "description": null
            }
        ],
        "references": [],
        "name": "pe_features"
    },
    {
        "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": "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": 1512,
                        "stack_dep_bypass": 0,
                        "stack_pivoted": 0,
                        "heap_dep_bypass": 0,
                        "length": 36864,
                        "protection": 64,
                        "process_handle": "0xffffffff",
                        "base_address": "0x00413000"
                    },
                    "time": 1603792386.812875,
                    "tid": 2732,
                    "flags": {
                        "protection": "PAGE_EXECUTE_READWRITE"
                    }
                },
                "pid": 1512,
                "type": "call",
                "cid": 6
            }
        ],
        "references": [],
        "name": "allocates_rwx"
    },
    {
        "markcount": 4,
        "families": [],
        "description": "The binary likely contains encrypted or compressed data indicative of a packer",
        "severity": 2,
        "marks": [
            {
                "entropy": 7.416165208931902,
                "section": {
                    "size_of_data": "0x00012000",
                    "virtual_address": "0x00013000",
                    "entropy": 7.416165208931902,
                    "name": ".rdata",
                    "virtual_size": "0x00011a96"
                },
                "type": "generic",
                "description": "A section with a high entropy has been found"
            },
            {
                "entropy": 6.948901320714539,
                "section": {
                    "size_of_data": "0x00006000",
                    "virtual_address": "0x0002c000",
                    "entropy": 6.948901320714539,
                    "name": ".kindata",
                    "virtual_size": "0x00005150"
                },
                "type": "generic",
                "description": "A section with a high entropy has been found"
            },
            {
                "entropy": 7.779176479911161,
                "section": {
                    "size_of_data": "0x00009000",
                    "virtual_address": "0x00032000",
                    "entropy": 7.779176479911161,
                    "name": ".bigup",
                    "virtual_size": "0x00008667"
                },
                "type": "generic",
                "description": "A section with a high entropy has been found"
            },
            {
                "entropy": 0.55,
                "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.1268131732940674,
            "dport": 137,
            "sport": 137
        },
        {
            "src": "192.168.56.101",
            "dst": "192.168.56.255",
            "offset": 5226,
            "time": 9.219688177108765,
            "dport": 138,
            "sport": 138
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7070,
            "time": 3.0345780849456787,
            "dport": 5355,
            "sport": 51001
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7398,
            "time": 1.0120511054992676,
            "dport": 5355,
            "sport": 53595
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7726,
            "time": 3.0785651206970215,
            "dport": 5355,
            "sport": 53848
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 8054,
            "time": 1.5185539722442627,
            "dport": 5355,
            "sport": 54255
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 8382,
            "time": -0.0974738597869873,
            "dport": 5355,
            "sport": 55314
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 8710,
            "time": 1.5343492031097412,
            "dport": 1900,
            "sport": 1900
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 28120,
            "time": 1.0419161319732666,
            "dport": 3702,
            "sport": 49152
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 36504,
            "time": 3.1286230087280273,
            "dport": 1900,
            "sport": 53598
        }
    ],
    "dns_servers": [],
    "http": [],
    "icmp": [],
    "smtp": [],
    "tcp": [],
    "smtp_ex": [],
    "mitm": [],
    "hosts": [],
    "pcap_sha256": "c0d9836171886c7de3bbb666f4a212cdefe5b427901742db7dc81ed584f198d0",
    "dns": [],
    "http_ex": [],
    "domains": [],
    "dead_hosts": [],
    "sorted_pcap_sha256": "6dd2afd958a65655c2fd5eb21c8a79ae2a55a2c5c4906f8d99c377964fd4076e",
    "irc": [],
    "https_ex": []
}

Screenshots

Screenshot from the sandbox

jsmk2202.exe removal instructions

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

Error Messages

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

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

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

jsmk2202.exe has stopped working.

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

jsmk2202.exe is not a valid Win32 application.

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

What will you do with jsmk2202.exe?

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