Suspicious multiple logins

[ArturNo]

Hi, thanks for your attention.

When I got to my computer today I noticed that it was turned on at the login screen, I check my event logs and in the security section I found several logins. I was not at home at that time so it was not me, I do not know much about what does event logs means so I would like to ask here if those logins were successful and if I could be being hacked or if it was some family member. As far as I know, no one knows my password.

Audit Success 02/10/2015 10:19:49 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 10:19:49 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 10:19:49 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 10:19:49 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 10:16:21 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 10:16:21 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 10:16:21 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 10:16:21 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 10:09:19 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 10:09:19 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 10:09:17 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 10:09:17 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 10:09:13 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 10:09:13 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 10:01:17 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 10:01:17 Microsoft Windows security auditing. 4624 Logon
Audit Failure 02/10/2015 09:59:15 Microsoft Windows security auditing. 5061 System Integrity
Audit Failure 02/10/2015 09:59:15 Microsoft Windows security auditing. 5061 System Integrity
Audit Failure 02/10/2015 09:59:15 Microsoft Windows security auditing. 5061 System Integrity
Audit Failure 02/10/2015 09:59:15 Microsoft Windows security auditing. 5061 System Integrity
Audit Success 02/10/2015 09:59:15 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 09:59:15 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:05 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:05 Microsoft Windows security auditing. 5024 Other System Events
Audit Success 02/10/2015 09:59:05 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 09:59:05 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:04 Microsoft Windows security auditing. 5033 Other System Events
Audit Success 02/10/2015 09:59:04 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 09:59:04 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:04 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 09:59:04 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:04 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 09:59:04 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:03 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 09:59:03 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4648 Logon
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4672 Special Logon
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4902 Audit Policy Change
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4624 Logon
Audit Success 02/10/2015 09:59:00 Microsoft Windows security auditing. 4608 Security State Change


Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 02/10/2015 09:59:00
Event ID: 4672
Task Category: Special Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: *****PC
Description:
Special privileges assigned to new logon.

Subject:
Security ID: Serviço de rede
Account Name: Serviço de rede
Account Domain: NT AUTHORITY
Logon ID: 0x3E4

Privileges: SeAssignPrimaryTokenPrivilege
SeAuditPrivilege
SeImpersonatePrivilege
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>4672</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12548</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2015-10-02T08:59:00.418849100Z" />
<EventRecordID>47463</EventRecordID>
<Correlation />
<Execution ProcessID="960" ThreadID="344" />
<Channel>Security</Channel>
<Computer>*****PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-20</Data>
<Data Name="SubjectUserName">Serviço de rede</Data>
<Data Name="SubjectDomainName">NT AUTHORITY</Data>
<Data Name="SubjectLogonId">0x3e4</Data>
<Data Name="PrivilegeList">SeAssignPrimaryTokenPrivilege
SeAuditPrivilege
SeImpersonatePrivilege</Data>
</EventData>
</Event>

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 02/10/2015 09:59:00
Event ID: 4902
Task Category: Audit Policy Change
Level: Information
Keywords: Audit Success
User: N/A
Computer: *****PC
Description:
The Per-user audit policy table was created.

Number of Elements: 0
Policy ID: 0xD42E
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>4902</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>13568</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2015-10-02T08:59:00.274454600Z" />
<EventRecordID>47459</EventRecordID>
<Correlation />
<Execution ProcessID="960" ThreadID="92" />
<Channel>Security</Channel>
<Computer>*****PC</Computer>
<Security />
</System>
<EventData>
<Data Name="PuaCount">0</Data>
<Data Name="PuaPolicyId">0xd42e</Data>
</EventData>
</Event>

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 02/10/2015 09:59:00
Event ID: 4624
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: *****PC
Description:
An account was successfully logged on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0

Logon Type: 0

Impersonation Level: -

New Logon:
Security ID: SYSTEM
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x3E7
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x4
Process Name:

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

Detailed Authentication Information:
Logon Process: -
Authentication Package: -
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>1</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2015-10-02T08:59:00.211949200Z" />
<EventRecordID>47458</EventRecordID>
<Correlation />
<Execution ProcessID="960" ThreadID="964" />
<Channel>Security</Channel>
<Computer>*****PC</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-5-18</Data>
<Data Name="TargetUserName">SYSTEM</Data>
<Data Name="TargetDomainName">NT AUTHORITY</Data>
<Data Name="TargetLogonId">0x3e7</Data>
<Data Name="LogonType">0</Data>
<Data Name="LogonProcessName">-</Data>
<Data Name="AuthenticationPackageName">-</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">0x4</Data>
<Data Name="ProcessName">
</Data>
<Data Name="IpAddress">-</Data>
<Data Name="IpPort">-</Data>
<Data Name="ImpersonationLevel">-</Data>
</EventData>
</Event>




Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 02/10/2015 09:59:00
Event ID: 4608
Task Category: Security State Change
Level: Information
Keywords: Audit Success
User: N/A
Computer: *****PC
Description:
Windows is starting up.

This event is logged when LSASS.EXE starts and the auditing subsystem is initialized.
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>4608</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12288</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2015-10-02T08:59:00.211949200Z" />
<EventRecordID>47457</EventRecordID>
<Correlation />
<Execution ProcessID="960" ThreadID="964" />
<Channel>Security</Channel>
<Computer>*****PC</Computer>
<Security />
</System>
<EventData>
</EventData>
</Event>

 

[Dark Lord of Tech]

http://www.sevenforums.com/system-security/194890-unauthorized-access-help-interpreting-event-viewer.html