What is aaLogger.exe?

aaLogger.exe is part of Wonderware Logger and developed by AVEVA Software, LLC according to the aaLogger.exe version information.

aaLogger.exe's description is "aaLogger Module"

aaLogger.exe is digitally signed by AVEVA Group plc.

aaLogger.exe is usually located in the 'C:\Program Files (x86)\Common Files\ArchestrA\' folder.

None of the anti-virus scanners at VirusTotal reports anything malicious about aaLogger.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 aaLogger.exe:

PropertyValue
Product nameWonderware Logger
Company nameAVEVA Software, LLC
File descriptionaaLogger Module
Original filenameaaLogger.exe
Legal copyrightCopyright 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
Legal trademarkRefer to: https://sw.aveva.com/legal/trademarks
Product version2.0.24500
File version2018.1119.2879.1

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

Product nameWonderware Logger
Company nameAVEVA Software, LLC
File descriptionaaLogger Module
Original filenameaaLogger.exe
Legal copyrightCopyright 2018 AVEVA Group plc and i..
Legal trademarkRefer to: https://sw.aveva.com/legal..
Product version2.0.24500
File version2018.1119.2879.1

Digital signatures [?]

aaLogger.exe has a valid digital signature.

PropertyValue
Signer nameAVEVA Group plc
Certificate issuer nameDigiCert SHA2 Assured ID Code Signing CA
Certificate serial number021527b486e924aac408d91bf154704e

VirusTotal report

None of the 70 anti-virus programs at VirusTotal detected the aaLogger.exe file.

None of the 70 anti-virus programs detected the aaLogger.exe file.

Sandbox Report

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

Summary

Successfully executed process in sandbox.

Generic

[
    {
        "process_path": "C:\\Windows\\System32\\lsass.exe",
        "process_name": "lsass.exe",
        "pid": 476,
        "summary": {},
        "first_seen": 1571961184.3438,
        "ppid": 376
    },
    {
        "process_path": "C:\\Users\\cuck\\AppData\\Local\\Temp\\19d18a63164d5701a9bc3d3caed68c16e045204e43e7e9df42fcbf929a761322.bin",
        "process_name": "19d18a63164d5701a9bc3d3caed68c16e045204e43e7e9df42fcbf929a761322.bin",
        "pid": 2460,
        "summary": {},
        "first_seen": 1571961184.7344,
        "ppid": 2740
    }
]

Signatures

[
    {
        "markcount": 1,
        "families": [],
        "description": "This executable has a PDB path",
        "severity": 1,
        "marks": [
            {
                "category": "pdb_path",
                "ioc": "E:\\BldSrc\\218\\2164\\Binaries\\Win32\\aaLogger.pdb",
                "type": "ioc",
                "description": null
            }
        ],
        "references": [],
        "name": "has_pdb"
    }
]

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": 662,
            "time": 6.2558550834656,
            "dport": 137,
            "sport": 137
        },
        {
            "src": "192.168.56.101",
            "dst": "192.168.56.255",
            "offset": 5342,
            "time": 12.347638130188,
            "dport": 138,
            "sport": 138
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7186,
            "time": 6.1631951332092,
            "dport": 5355,
            "sport": 51001
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7514,
            "time": 4.1639621257782,
            "dport": 5355,
            "sport": 53595
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 7842,
            "time": 6.2072479724884,
            "dport": 5355,
            "sport": 53848
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 8170,
            "time": 4.6626110076904,
            "dport": 5355,
            "sport": 54255
        },
        {
            "src": "192.168.56.101",
            "dst": "224.0.0.252",
            "offset": 8498,
            "time": 3.0557990074158,
            "dport": 5355,
            "sport": 55314
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 8826,
            "time": 4.6911361217499,
            "dport": 1900,
            "sport": 1900
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 28236,
            "time": 4.2206330299377,
            "dport": 3702,
            "sport": 49152
        },
        {
            "src": "192.168.56.101",
            "dst": "239.255.255.250",
            "offset": 36620,
            "time": 6.2693400382996,
            "dport": 1900,
            "sport": 53598
        }
    ],
    "dns_servers": [],
    "http": [],
    "icmp": [],
    "smtp": [],
    "tcp": [],
    "smtp_ex": [],
    "mitm": [],
    "hosts": [],
    "pcap_sha256": "46658b0c7a59e12ec038bfca713ad2c681a7dbe84ff118f061415866c18163df",
    "dns": [],
    "http_ex": [],
    "domains": [],
    "dead_hosts": [],
    "sorted_pcap_sha256": "ab0a8d2f80a830efacef7ff93212b915df14565e0933fe784631fea7057e771a",
    "irc": [],
    "https_ex": []
}

Screenshots

Screenshot from the sandboxScreenshot from the sandboxScreenshot from the sandbox

TCP/UDP Listening Ports [?]

aaLogger.exe has been reported to listen on the following TCP/UDP ports.

PortProtocol# Occurrences
49669TCP v61

Hashes [?]

PropertyValue
MD5ea443d97f3d77e4f05b1d14a5518ed7c
SHA25619d18a63164d5701a9bc3d3caed68c16e045204e43e7e9df42fcbf929a761322

Error Messages

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

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

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

aaLogger Module has stopped working.

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

aalogger.exe is not a valid Win32 application.

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

What will you do with aaLogger.exe?

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



Malware or legitimate?

If you feel that you need more information to determine if your should keep this file or remove it, please read this guide.

Please select the option that best describe your thoughts on the information provided on this web page


Free online surveys

And now some shameless self promotion ;)

A screenshot of FreeFixer's scan result.Hi, my name is Roger Karlsson. I've been running this website since 2006. I want to let you know about the FreeFixer program. FreeFixer is a freeware tool that analyzes your system and let you manually identify unwanted programs. Once you've identified some malware files, FreeFixer is pretty good at removing them. You can download FreeFixer here. It runs on Windows 2000/XP/2003/2008/2016/2019/Vista/7/8/8.1/10. Supports both 32- and 64-bit Windows.

If you have questions, feedback on FreeFixer or the freefixer.com website, need help analyzing FreeFixer's scan result or just want to say hello, please contact me. You can find my email address at the contact page.

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