Logon Type 2 - Strange Activity

Graham Smith 1 Reputation point
2021-04-14T12:05:55.543+00:00

This morning I noticed some strange activity last night on my event viewer. I checked it after seeing in my internet history that the Microsoft Edge had accessed two sites at 12.29am. See attached.

In my event log there is an event type 4624 logon type 2 at 12.29am. Is this likely someone has physically logged onto my laptop or an automated event?

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 14/04/2021 00:27:27
Event ID: 4624
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: LAPTOP-DEGLLKRK
Description:
An account was successfully logged on.

Subject:
Security ID: SYSTEM
Account Name: LAPTOP-DEGLLKRK$
Account Domain: WORKGROUP
Logon ID: 0x3E7

Logon Information:
Logon Type: 2
Restricted Admin Mode: -
Virtual Account: Yes
Elevated Token: No

Impersonation Level: Impersonation

New Logon:
Security ID: Font Driver Host\UMFD-0
Account Name: UMFD-0
Account Domain: Font Driver Host
Logon ID: 0x11823
Linked Logon ID: 0x0
Network Account Name: -
Network Account Domain: -
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x228
Process Name: C:\Windows\System32\wininit.exe

Network Information:
Workstation Name: -
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The impersonation level field indicates the extent to which a process in the logon session can impersonate.

The authentication information fields provide detailed information about this specific logon request.

  • Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  • Transited services indicate which intermediate services have participated in this logon request.
  • Package name indicates which sub-protocol was used among the NTLM protocols.
  • Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" />
    <EventID>4624</EventID>
    <Version>2</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8020000000000000</Keywords>
    <TimeCreated SystemTime="2021-04-13T23:27:27.0704386Z" />
    <EventRecordID>134027</EventRecordID>
    <Correlation ActivityID="{8c64dc70-30bc-0002-fadc-648cbc30d701}" />
    <Execution ProcessID="1144" ThreadID="1228" />
    <Channel>Security</Channel>
    <Computer>LAPTOP-DEGLLKRK</Computer>
    <Security />
    </System>
    <EventData>
    <Data Name="SubjectUserSid">S-1-5-18</Data>
    <Data Name="SubjectUserName">LAPTOP-DEGLLKRK$</Data>
    <Data Name="SubjectDomainName">WORKGROUP</Data>
    <Data Name="SubjectLogonId">0x3e7</Data>
    <Data Name="TargetUserSid">S-1-5-96-0-0</Data>
    <Data Name="TargetUserName">UMFD-0</Data>
    <Data Name="TargetDomainName">Font Driver Host</Data>
    <Data Name="TargetLogonId">0x11823</Data>
    <Data Name="LogonType">2</Data>
    <Data Name="LogonProcessName">Advapi </Data>
    <Data Name="AuthenticationPackageName">Negotiate</Data>
    <Data Name="WorkstationName">-</Data>
    <Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x228</Data>
    <Data Name="ProcessName">C:\Windows\System32\wininit.exe</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>
    <Data Name="ImpersonationLevel">%%1833</Data>
    <Data Name="RestrictedAdminMode">-</Data>
    <Data Name="TargetOutboundUserName">-</Data>
    <Data Name="TargetOutboundDomainName">-</Data>
    <Data Name="VirtualAccount">%%1842</Data>
    <Data Name="TargetLinkedLogonId">0x0</Data>
    <Data Name="ElevatedToken">%%1843</Data>
    </EventData>
    </Event>
Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,697 questions
Windows 10 Security
Windows 10 Security
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Security: The precautions taken to guard against crime, attack, sabotage, espionage, or another threat.
2,926 questions
{count} votes

3 answers

Sort by: Most helpful
  1. richard oconnor 1 Reputation point
    2023-01-02T13:13:04.98+00:00

    I have been working on this for a while now as I have about 8 pc's experiencing this as well . They are using font process , winlog on and consent.exe to log in but tracking them is difficult as I am still working on this . Has anyone had any success ?

    Using SOPHOS central to find what's going on as i have some decent logs but unable to id the process or the incoming ip address . I have a few log on's using guest NT Authority and adding in new log in names as they first attack the SAM entries in the registry taking over the device / pc . Trying to find how they are maneuvering also . Just discovered about 2 months ago !
    Found some strange ports on Process monitor but could not find out where on both sides ( IP Side and Internal side ) as I am working on this now !

    My Windows 11 Pro even after multiple times restoring has become seriously problematic at my house !

    The more I dig into this I find so many vulnerabilities !
    Looks like possible log4J but there are so many other relevant viruses that I am going around in circles attempting to id this !

    Does anyone here have a hardening guide ?

    Looking for Microsoft to lend a hand here !

    Regards

    Rich


  2. richard oconnor 1 Reputation point
    2023-01-02T15:49:31.527+00:00

    CVE-2020-1355]

    Does anyone know if this was resolved in Windows 11 Pro ?
    It looks like there are no resolutions to these vulnerabilities as the more I review the more I find and no answers to active remote vulnerabilities !
    Microsoft added so many features that they increased the hackers abilities !
    And we pay for them !

    0 comments No comments

  3. kevin cavelti 0 Reputation points
    2023-05-11T05:00:43.2666667+00:00

    Good day

    We have the same logins in the middle of the night.

    Have you found a solution or explanation for this?

    Greetings

    Kevin


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.