What is try2.exe?

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

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

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

Digital signatures [?]

try2.exe is not signed.

VirusTotal report

48 of the 64 anti-virus programs at VirusTotal detected the try2.exe file. That's a 75% detection rate.

ScannerDetection Name
Acronis suspicious
Ad-Aware Gen:Variant.Graftor.441733
AegisLab Trojan.Win32.Scrop.4!c
AhnLab-V3 Dropper/Win32.Scrop.R214215
Alibaba TrojanDropper:Win32/Scrop.46af603f
Antiy-AVL Trojan/MSIL.Revenge
Arcabit Trojan.Graftor.D6BD85
Avast Win32:Malware-gen
AVG Win32:Malware-gen
Avira HEUR/AGEN.1000015
BitDefender Gen:Variant.Graftor.441733
CAT-QuickHeal Trojan.IGENERIC
Comodo Malware@#1mhh488d6p9rg
CrowdStrike win/malicious_confidence_100% (W)
Cybereason malicious.cb6870
DrWeb Trojan.PWS.Stealer.19953
Emsisoft Gen:Variant.Graftor.441733 (B)
Endgame malicious (high confidence)
ESET-NOD32 a variant of Win32/Injector.DTSJ
F-Secure Heuristic.HEUR/AGEN.1000015
FireEye Generic.mg.7eeb2f0cb687020d
Fortinet W32/GenKryptik.AZYG!tr
GData Gen:Variant.Graftor.441733
Ikarus Trojan.Win32.Injector
Invincea heuristic
Jiangmin TrojanDropper.Scrop.vk
K7AntiVirus Trojan ( 0051c91a1 )
K7GW Trojan ( 0051c91a1 )
Kaspersky Trojan-Dropper.Win32.Scrop.eqt
MAX malware (ai score=94)
McAfee Packed-VA!7EEB2F0CB687
McAfee-GW-Edition BehavesLike.Win32.AdwareDealPly.jc
Microsoft Trojan:Win32/Skeeyah.A!rfn
MicroWorld-eScan Gen:Variant.Graftor.441733
NANO-Antivirus Trojan.Win32.Stealer.evlbof
Paloalto generic.ml
Panda Trj/CI.A
Qihoo-360 HEUR/QVM20.1.92C3.Malware.Gen
Rising Trojan.Injector!1.AE36 (CLOUD)
SentinelOne DFI - Malicious PE
Sophos Mal/Fareit-O
Tencent Win32.Trojan-dropper.Scrop.Angl
TrendMicro-HouseCall TROJ_GEN.R002C0PB419
VBA32 TrojanDropper.Scrop
Yandex Trojan.DR.Scrop!
Zillya Backdoor.Androm.Win32.48002
ZoneAlarm Trojan-Dropper.Win32.Scrop.eqt
Zoner Trojan.Win32.63507
48 of the 64 anti-virus programs detected the try2.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\\Borland\\Delphi\\Locales",
        "HKEY_LOCAL_MACHINE\\Software\\Borland\\Locales",
        "HKEY_CURRENT_USER\\Software\\Borland\\Locales"
    ],
    "regkey_read": [
        "HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\Nls\\CustomLocale\\en-US",
        "HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\Nls\\ExtendedLocale\\en-US"
    ],
    "dll_loaded": [
        "dwmapi.dll"
    ]
}

Generic

[
    {
        "process_path": "C:\\Users\\cuck\\AppData\\Local\\Temp\\6b65d074da26378d5e47b7aa3485be77d3b273d0641b06fb6624f3041aa442d5.bin",
        "process_name": "6b65d074da26378d5e47b7aa3485be77d3b273d0641b06fb6624f3041aa442d5.bin",
        "pid": 2740,
        "summary": {
            "regkey_opened": [
                "HKEY_CURRENT_USER\\Software\\Borland\\Delphi\\Locales",
                "HKEY_LOCAL_MACHINE\\Software\\Borland\\Locales",
                "HKEY_CURRENT_USER\\Software\\Borland\\Locales"
            ],
            "regkey_read": [
                "HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\Nls\\CustomLocale\\en-US",
                "HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\Nls\\ExtendedLocale\\en-US"
            ],
            "dll_loaded": [
                "dwmapi.dll"
            ]
        },
        "first_seen": 1582404795.65625,
        "ppid": 1664
    },
    {
        "process_path": "C:\\Windows\\System32\\lsass.exe",
        "process_name": "lsass.exe",
        "pid": 476,
        "summary": {},
        "first_seen": 1582404795.328125,
        "ppid": 376
    }
]

Signatures

[
    {
        "markcount": 3,
        "families": [],
        "description": "The executable contains unknown PE section names indicative of a packer (could be a false positive)",
        "severity": 1,
        "marks": [
            {
                "category": "section",
                "ioc": "CODE",
                "type": "ioc",
                "description": null
            },
            {
                "category": "section",
                "ioc": "DATA",
                "type": "ioc",
                "description": null
            },
            {
                "category": "section",
                "ioc": "BSS",
                "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": "NtAllocateVirtualMemory",
                    "return_value": 0,
                    "arguments": {
                        "process_identifier": 2740,
                        "region_size": 4096,
                        "stack_dep_bypass": 0,
                        "stack_pivoted": 0,
                        "heap_dep_bypass": 0,
                        "protection": 64,
                        "process_handle": "0xffffffff",
                        "allocation_type": 4096,
                        "base_address": "0x00360000"
                    },
                    "time": 1582404795.79625,
                    "tid": 2436,
                    "flags": {
                        "protection": "PAGE_EXECUTE_READWRITE",
                        "allocation_type": "MEM_COMMIT"
                    }
                },
                "pid": 2740,
                "type": "call",
                "cid": 128
            }
        ],
        "references": [],
        "name": "allocates_rwx"
    }
]

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.1114931106567383,
            "dport": 137,
            "sport": 137
        },
        {
            "src": "192.168.56.101",
            "dst": "192.168.56.255",
            "offset": 5226,
            "time": 9.172879219055176,
            "dport": 138,
            "sport": 138
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7070,
            "time": 3.0116209983825684,
            "dport": 5355,
            "sport": 51001
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7398,
            "time": 1.0535030364990234,
            "dport": 5355,
            "sport": 53595
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7726,
            "time": 3.063751220703125,
            "dport": 5355,
            "sport": 53848
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 8054,
            "time": 1.5664610862731934,
            "dport": 5355,
            "sport": 54255
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 8382,
            "time": -0.08095192909240723,
            "dport": 5355,
            "sport": 55314
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 8710,
            "time": 1.5625090599060059,
            "dport": 1900,
            "sport": 1900
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 28120,
            "time": 1.0745069980621338,
            "dport": 3702,
            "sport": 49152
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 36504,
            "time": 3.156872034072876,
            "dport": 1900,
            "sport": 53598
        }
    ],
    "dns_servers": [],
    "http": [],
    "icmp": [],
    "smtp": [],
    "tcp": [],
    "smtp_ex": [],
    "mitm": [],
    "hosts": [],
    "pcap_sha256": "605a8bd64b97e4d10e9d85c6e2de3ba922766b4d1c5bb55fe0ae55f5fa5ad87d",
    "dns": [],
    "http_ex": [],
    "domains": [],
    "dead_hosts": [],
    "sorted_pcap_sha256": "ed3615ee76feb1d6dd44712f6478a75fa2dac36c31c5495ed1db86bbe98afd78",
    "irc": [],
    "https_ex": []
}

Screenshots

Screenshot from the sandboxScreenshot from the sandboxScreenshot from the sandboxScreenshot from the sandboxScreenshot from the sandboxScreenshot from the sandboxScreenshot from the sandbox

try2.exe removal instructions

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

Error Messages

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

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

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

try2.exe has stopped working.

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

try2.exe is not a valid Win32 application.

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

What will you do with try2.exe?

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