What is war.exe?

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

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

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

Digital signatures [?]

war.exe is not signed.

VirusTotal report

48 of the 66 anti-virus programs at VirusTotal detected the war.exe file. That's a 73% detection rate.

ScannerDetection Name
Acronis suspicious
Ad-Aware Trojan.Agent.DTZR
AegisLab Trojan.Win32.Noon.4!c
AhnLab-V3 Win-Trojan/Delphiless.Exp
Alibaba Trojan:Win32/Injector.99a4e42e
ALYac Trojan.Agent.DTZR
Antiy-AVL Trojan[Spy]/Win32.Noon
Arcabit Trojan.Agent.DTZR
Avast Win32:Malware-gen
AVG Win32:Malware-gen
Avira TR/Injector.egjgk
BitDefender Trojan.Agent.DTZR
ClamAV Win.Malware.Ursu-6933911-0
CrowdStrike win/malicious_confidence_90% (W)
Cybereason malicious.e7e27f
Cyren W32/Injector.LJGP-2023
DrWeb Trojan.Nanocore.23
Emsisoft Trojan.Agent.DTZR (B)
Endgame malicious (high confidence)
ESET-NOD32 a variant of Win32/Injector.EEUA
F-Secure Trojan.TR/Injector.egjgk
FireEye Generic.mg.c2d138b5e7e2f433
Fortinet W32/Kryptik.GLZZ!tr
GData Trojan.Agent.DTZR
Ikarus Trojan-Spy.LokiBot
Invincea heuristic
Jiangmin TrojanSpy.Noon.fyl
K7AntiVirus Trojan ( 0054b7a01 )
K7GW Trojan ( 0054b7a01 )
Kaspersky HEUR:Trojan-Spy.Win32.Noon.gen
Malwarebytes Trojan.Injector
MAX malware (ai score=100)
McAfee Fareit-FKV!C2D138B5E7E2
McAfee-GW-Edition BehavesLike.Win32.Fareit.hh
Microsoft Trojan:Win32/Skeeyah.A!rfn
MicroWorld-eScan Trojan.Agent.DTZR
NANO-Antivirus Trojan.Win32.GenKryptik.foxeqa
Paloalto generic.ml
Panda Trj/Genetic.gen
Qihoo-360 Win32/Trojan.Spy.9dd
Rising Trojan.Injector!1.AFE3 (CLASSIC)
SentinelOne DFI - Suspicious PE
Sophos Mal/Fareit-Q
Trapmine malicious.high.ml.score
TrendMicro-HouseCall TrojanSpy.Win32.LOKI.SMD1.hp
VBA32 TrojanSpy.Noon
ZoneAlarm HEUR:Trojan-Spy.Win32.Noon.gen
Zoner Trojan.Win32.76522
48 of the 66 anti-virus programs detected the war.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\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\GRE_Initialize\\DisableMetaFiles",
        "HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\Nls\\CustomLocale\\en-US",
        "HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\Nls\\ExtendedLocale\\en-US"
    ],
    "dll_loaded": [
        "dwmapi.dll",
        "advapi32",
        "user32",
        "shell32",
        "olepro32.dll"
    ]
}

Generic

[
    {
        "process_path": "C:\\Users\\cuck\\AppData\\Local\\Temp\\e6d2bfdaa0cc322bc31c02f778c29f93bdf97f67da529131697cf31a2bef6975.bin",
        "process_name": "e6d2bfdaa0cc322bc31c02f778c29f93bdf97f67da529131697cf31a2bef6975.bin",
        "pid": 2816,
        "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\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\GRE_Initialize\\DisableMetaFiles",
                "HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\Nls\\CustomLocale\\en-US",
                "HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\Nls\\ExtendedLocale\\en-US"
            ],
            "dll_loaded": [
                "dwmapi.dll",
                "advapi32",
                "user32",
                "shell32",
                "olepro32.dll"
            ]
        },
        "first_seen": 1582368785.671875,
        "ppid": 2660
    },
    {
        "process_path": "C:\\Windows\\System32\\lsass.exe",
        "process_name": "lsass.exe",
        "pid": 476,
        "summary": {},
        "first_seen": 1582368785.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": "The executable uses a known packer",
        "severity": 1,
        "marks": [
            {
                "category": "packer",
                "ioc": "BobSoft Mini Delphi -> BoB \/ BobSoft",
                "type": "ioc",
                "description": null
            }
        ],
        "references": [],
        "name": "peid_packer"
    },
    {
        "markcount": 3,
        "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": 2816,
                        "region_size": 4096,
                        "stack_dep_bypass": 0,
                        "stack_pivoted": 0,
                        "heap_dep_bypass": 0,
                        "protection": 64,
                        "process_handle": "0xffffffff",
                        "allocation_type": 4096,
                        "base_address": "0x007a0000"
                    },
                    "time": 1582368785.796875,
                    "tid": 2420,
                    "flags": {
                        "protection": "PAGE_EXECUTE_READWRITE",
                        "allocation_type": "MEM_COMMIT"
                    }
                },
                "pid": 2816,
                "type": "call",
                "cid": 105
            },
            {
                "call": {
                    "category": "process",
                    "status": 1,
                    "stacktrace": [],
                    "api": "NtProtectVirtualMemory",
                    "return_value": 0,
                    "arguments": {
                        "process_identifier": 2816,
                        "stack_dep_bypass": 0,
                        "stack_pivoted": 0,
                        "heap_dep_bypass": 1,
                        "length": 28672,
                        "protection": 64,
                        "process_handle": "0xffffffff",
                        "base_address": "0x01de1000"
                    },
                    "time": 1582368793.171875,
                    "tid": 2420,
                    "flags": {
                        "protection": "PAGE_EXECUTE_READWRITE"
                    }
                },
                "pid": 2816,
                "type": "call",
                "cid": 481
            },
            {
                "call": {
                    "category": "process",
                    "status": 1,
                    "stacktrace": [],
                    "api": "NtAllocateVirtualMemory",
                    "return_value": 0,
                    "arguments": {
                        "process_identifier": 2816,
                        "region_size": 4096,
                        "stack_dep_bypass": 0,
                        "stack_pivoted": 0,
                        "heap_dep_bypass": 0,
                        "protection": 64,
                        "process_handle": "0xffffffff",
                        "allocation_type": 12288,
                        "base_address": "0x007e0000"
                    },
                    "time": 1582368793.171875,
                    "tid": 2420,
                    "flags": {
                        "protection": "PAGE_EXECUTE_READWRITE",
                        "allocation_type": "MEM_COMMIT|MEM_RESERVE"
                    }
                },
                "pid": 2816,
                "type": "call",
                "cid": 486
            }
        ],
        "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.179813963852573,
                "section": {
                    "size_of_data": "0x00020200",
                    "virtual_address": "0x0007a000",
                    "entropy": 7.179813963852573,
                    "name": ".rsrc",
                    "virtual_size": "0x00020068"
                },
                "type": "generic",
                "description": "A section with a high entropy has been found"
            },
            {
                "entropy": 0.2166947723440135,
                "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"
    },
    {
        "markcount": 1,
        "families": [],
        "description": "Expresses interest in specific running processes",
        "severity": 2,
        "marks": [
            {
                "category": "process",
                "ioc": "e6d2bfdaa0cc322bc31c02f778c29f93bdf97f67da529131697cf31a2bef6975.bin",
                "type": "ioc",
                "description": null
            }
        ],
        "references": [],
        "name": "process_interest"
    }
]

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.0782461166381836,
            "dport": 137,
            "sport": 137
        },
        {
            "src": "192.168.56.101",
            "dst": "192.168.56.255",
            "offset": 5226,
            "time": 9.0782310962677,
            "dport": 138,
            "sport": 138
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7070,
            "time": 3.041656970977783,
            "dport": 5355,
            "sport": 51001
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7398,
            "time": 1.0333850383758545,
            "dport": 5355,
            "sport": 53595
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7726,
            "time": 3.053818941116333,
            "dport": 5355,
            "sport": 53848
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 8054,
            "time": 1.5351641178131104,
            "dport": 5355,
            "sport": 54255
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 8382,
            "time": -0.08415889739990234,
            "dport": 5355,
            "sport": 55314
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 8710,
            "time": 1.5624501705169678,
            "dport": 1900,
            "sport": 1900
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 28120,
            "time": 1.066514015197754,
            "dport": 3702,
            "sport": 49152
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 36504,
            "time": 3.1245479583740234,
            "dport": 1900,
            "sport": 53598
        }
    ],
    "dns_servers": [],
    "http": [],
    "icmp": [],
    "smtp": [],
    "tcp": [],
    "smtp_ex": [],
    "mitm": [],
    "hosts": [],
    "pcap_sha256": "5a39d9194690c7ea7c316bf9aa5a43326bc4e3eb18ce2e5e34ebc171880eab80",
    "dns": [],
    "http_ex": [],
    "domains": [],
    "dead_hosts": [],
    "sorted_pcap_sha256": "ced85acfaeacbb66c259915dfe19c87b40a00c98a9069c788cfdf3efe8259228",
    "irc": [],
    "https_ex": []
}

Screenshots

Screenshot from the sandbox

war.exe removal instructions

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

Error Messages

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

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

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

war.exe has stopped working.

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

war.exe is not a valid Win32 application.

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

What will you do with war.exe?

To help other users, please let us know what you will do with war.exe:



What did other users do?

The poll result listed below shows what users chose to do with war.exe. 0% have voted for removal. Based on votes from 1 user.

Votes
Keep100 %
1
Remove0 %
0

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