What is NjY4ODAyM2M.exe?

NjY4ODAyM2M.exe is digitally signed by chavanactechnology.com.

NjY4ODAyM2M.exe is usually located in the 'C:\Program Files\Y2MyZDk2NzI2NzFiO\' folder.

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

PropertyValue
Legal copyrightCopyright (C) 2018
Product version13.14.1.312
File version13.14.1.312

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

Legal copyrightCopyright (C) 2018
Product version13.14.1.312
File version13.14.1.312

Digital signatures [?]

NjY4ODAyM2M.exe has a valid digital signature.

PropertyValue
Signer namechavanactechnology.com
Certificate issuer nameGlobalSign CodeSigning CA - G3
Certificate serial number2aa7c828e42df6c2274716d5

VirusTotal report

7 of the 69 anti-virus programs at VirusTotal detected the NjY4ODAyM2M.exe file. That's a 10% detection rate.

ScannerDetection Name
Malwarebytes Adware.Zdengo
McAfee Artemis!A1CB84BC3B8C
McAfee-GW-Edition Artemis
Microsoft PUA:Win32/Wajam
Rising PUA.Wajam!8.F0 (CLOUD)
VBA32 BScope.TrojanDownloader.Adload
Webroot W32.Malware.Gen
7 of the 69 anti-virus programs detected the NjY4ODAyM2M.exe file.

Sandbox Report

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

Summary

Successfully executed process in sandbox.

Summary

{
    "directory_enumerated": [
        "C:\\Users\\cuck\\AppData\\Local\\Temp\\*.dll",
        "C:\\Users\\cuck\\AppData\\Local\\Temp\\*.dat",
        "C:\\Users\\cuck\\AppData\\Local\\Temp\\*.patcher",
        "C:\\Users\\cuck\\AppData\\Local\\Temp\\service.dat"
    ],
    "dll_loaded": [
        "kernel32",
        "api-ms-win-core-fibers-l1-1-1",
        "api-ms-win-core-localization-l1-2-1",
        "api-ms-win-appmodel-runtime-l1-1-1",
        "Kernel32.dll",
        "ext-ms-win-kernel32-package-current-l1-1-0",
        "advapi32",
        "Ole32.dll",
        "api-ms-win-core-synch-l1-2-0"
    ],
    "regkey_read": [
        "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\GRE_Initialize\\DisableMetaFiles"
    ]
}

Generic

[
    {
        "process_path": "C:\\Users\\cuck\\AppData\\Local\\Temp\\f47c8166a6e4d2030f5d846503e9588f34e4a03665876f49e6f17435be138c94.bin",
        "process_name": "f47c8166a6e4d2030f5d846503e9588f34e4a03665876f49e6f17435be138c94.bin",
        "pid": 2888,
        "summary": {
            "directory_enumerated": [
                "C:\\Users\\cuck\\AppData\\Local\\Temp\\*.dll",
                "C:\\Users\\cuck\\AppData\\Local\\Temp\\*.dat",
                "C:\\Users\\cuck\\AppData\\Local\\Temp\\*.patcher",
                "C:\\Users\\cuck\\AppData\\Local\\Temp\\service.dat"
            ],
            "dll_loaded": [
                "kernel32",
                "api-ms-win-core-fibers-l1-1-1",
                "api-ms-win-core-localization-l1-2-1",
                "api-ms-win-appmodel-runtime-l1-1-1",
                "Kernel32.dll",
                "ext-ms-win-kernel32-package-current-l1-1-0",
                "advapi32",
                "Ole32.dll",
                "api-ms-win-core-synch-l1-2-0"
            ],
            "regkey_read": [
                "HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\GRE_Initialize\\DisableMetaFiles"
            ]
        },
        "first_seen": 1604346788.796875,
        "ppid": 2016
    },
    {
        "process_path": "C:\\Windows\\System32\\lsass.exe",
        "process_name": "lsass.exe",
        "pid": 476,
        "summary": {},
        "first_seen": 1604346788.453125,
        "ppid": 376
    }
]

Signatures

[
    {
        "markcount": 1,
        "families": [],
        "description": "This executable has a PDB path",
        "severity": 1,
        "marks": [
            {
                "category": "pdb_path",
                "ioc": "Z:\\194\\qVZRh3\\df\\G0ZPyPpRCq\\IaNmreOiOVB7J\\RPv67KboRy6o8qv\\VAoOvNQ9Rg\\tLsh473XRweSnB\\qrE7lMFTeL0C\\J3wMT9OOMU4A\\bTQLiMxUM0C.pdb",
                "type": "ioc",
                "description": null
            }
        ],
        "references": [],
        "name": "has_pdb"
    },
    {
        "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": ".gfids",
                "type": "ioc",
                "description": null
            }
        ],
        "references": [],
        "name": "pe_features"
    },
    {
        "markcount": 2,
        "families": [],
        "description": "The binary likely contains encrypted or compressed data indicative of a packer",
        "severity": 2,
        "marks": [
            {
                "entropy": 6.9640649521366615,
                "section": {
                    "size_of_data": "0x0013a000",
                    "virtual_address": "0x00075000",
                    "entropy": 6.9640649521366615,
                    "name": ".rsrc",
                    "virtual_size": "0x00139fd9"
                },
                "type": "generic",
                "description": "A section with a high entropy has been found"
            },
            {
                "entropy": 0.7295962823119373,
                "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.078965902328491,
            "dport": 137,
            "sport": 137
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 2018,
            "time": 3.0343480110168457,
            "dport": 5355,
            "sport": 51001
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 2346,
            "time": 1.018885850906372,
            "dport": 5355,
            "sport": 53595
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 2674,
            "time": 3.048429012298584,
            "dport": 5355,
            "sport": 53848
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 3002,
            "time": 1.630486011505127,
            "dport": 5355,
            "sport": 54255
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 3330,
            "time": -0.09698104858398438,
            "dport": 5355,
            "sport": 55314
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 3658,
            "time": 1.5485119819641113,
            "dport": 1900,
            "sport": 1900
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 6986,
            "time": 1.0473558902740479,
            "dport": 3702,
            "sport": 49152
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 11178,
            "time": 3.095120906829834,
            "dport": 1900,
            "sport": 53598
        }
    ],
    "dns_servers": [],
    "http": [],
    "icmp": [],
    "smtp": [],
    "tcp": [],
    "smtp_ex": [],
    "mitm": [],
    "hosts": [],
    "pcap_sha256": "05a90dc7233eed9eb82641b59430fc7c810971704f1810e43541b40184d0a077",
    "dns": [],
    "http_ex": [],
    "domains": [],
    "dead_hosts": [],
    "sorted_pcap_sha256": "4552a81290ac71980136b9cd2159e109ffeb3aadb8654eb3b9f0d67fa719e80c",
    "irc": [],
    "https_ex": []
}

Screenshots

Screenshot from the sandbox

NjY4ODAyM2M.exe removal instructions

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

Error Messages

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

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

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

njy4odaym2m.exe has stopped working.

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

njy4odaym2m.exe is not a valid Win32 application.

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

What will you do with the file?

To help other users, please let us know what you will do with the file:



What did other users do?

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

Votes
Keep0 %
0
Remove100 %
1

NOTE: Please do not use this poll as the only source of input to determine what you will do with the file. Only 1 user has voted so far so it does not offer a high degree of confidence.

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