Suspicious multiple logins

G

Guest

Guest
Hello i logged in my pc this morning

and checked windows logs - security i check it often to see whats going on

and i sore multiple logins deleted them restarted pc and logged back on checked again and it did the exact same logs at the same time something called advapi and logged in as anonymous user it looks very suspicious i'm afraid i might have a virus or that my computer has been in logged in by somebody other than me like remotely accessed also i never remotely access my computer and it never has been remotely accessed as far as i no i have scanned my pc with avg and malwarebytes both turned up clean but yea im no expert but i reckon it looked suspicious and im kinda fearful as to what possibly is going on here if anything

i have posted the full event table and the Partial Concerning descriptions below i have hashed all names and user id's

all names where given and specified on os install i double checked
your help and advice is appreciated thank you

Audit Success 28/11/2013 8:01:03 AM Microsoft Windows security auditing. 4648 Logon
Audit Success 28/11/2013 8:01:03 AM Microsoft Windows security auditing. 4624 Logon
Audit Success 28/11/2013 8:01:03 AM Microsoft Windows security auditing. 4672 Special Logon
Audit Success 28/11/2013 8:00:59 AM Microsoft Windows security auditing. 4624 Logon
Audit Success 28/11/2013 8:00:58 AM Microsoft Windows security auditing. 5024 Other System Events
Audit Success 28/11/2013 8:00:58 AM Microsoft Windows security auditing. 5033 Other System Events
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4624 Logon
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4672 Special Logon
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4624 Logon
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4672 Special Logon
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4672 Special Logon
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4624 Logon
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4624 Logon
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4672 Special Logon
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4624 Logon
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4672 Special Logon
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4902 Audit Policy Change
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4624 Logon
Audit Success 28/11/2013 8:00:57 AM Microsoft Windows security auditing. 4608 Security State Change
Audit Success 28/11/2013 8:00:11 AM Eventlog 1100 Service shutdown
Audit Success 28/11/2013 8:00:07 AM Microsoft Windows security auditing. 4647 Logoff
Audit Success 28/11/2013 7:55:20 AM Eventlog 1102 Log clear
.................................................................................................................................................
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 28/11/2013 8:01:03 AM
Event ID: 4648
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: xxxxxx
Description:
A logon was attempted using explicit credentials.

Subject:
Security ID: SYSTEM
Account Name: xxxxx$
Account Domain: HOME
Logon ID: 0x3e7
Logon GUID: {00000000-0000-0000-0000-000000000000}

Account Whose Credentials Were Used:
Account Name: XXXXXX
Account Domain: XXXXX
Logon GUID: {00000000-0000-0000-0000-000000000000}

Target Server:
Target Server Name: localhost
Additional Information: localhost

Process Information:
Process ID: 0x40c
Process Name: C:\Windows\System32\winlogon.exe

Network Information:
Network Address: #####
Port: 0

This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{xxxxx}" />
<EventID>4648</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2013-11-27T21:01:03.239815000Z" />
<EventRecordID>6538</EventRecordID>
<Correlation />
<Execution ProcessID="1048" ThreadID="2224" />
<Channel>Security</Channel>
<Computer>xxxxxx</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">xxxxxx$</Data>
<Data Name="SubjectDomainName">HOME</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TargetUserName">XXXXXX</Data>
<Data Name="TargetDomainName">xxxxxx</Data>
<Data Name="TargetLogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TargetServerName">localhost</Data>
<Data Name="TargetInfo">localhost</Data>
<Data Name="ProcessId">0x40c</Data>
<Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data>
<Data Name="IpAddress">127.0.0.1</Data>
<Data Name="IpPort">0</Data>
</EventData>
</Event>

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 28/11/2013 8:01:03 AM
Event ID: 4624
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: xxxxxx
Description:
An account was successfully logged on.

Subject:
Security ID: SYSTEM
Account Name: xxxxxxx$
Account Domain: HOME
Logon ID: 0x3e7

Logon Type: 2

New Logon:
Security ID: xxxxxxxx\XXXXX
Account Name: XXXXX
Account Domain: xxxxxx
Logon ID: 0x69a0a
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x40c
Process Name: C:\Windows\System32\winlogon.exe

Network Information:
Workstation Name: xxxx
Source Network Address: #####
Source Port: 0

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



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="{222222}" />
<EventID>4624</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2013-11-27T21:01:03.239815000Z" />
<EventRecordID>6539</EventRecordID>
<Correlation />
<Execution ProcessID="1048" ThreadID="2224" />
<Channel>Security</Channel>
<Computer>xxxxx</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-18</Data>
<Data Name="SubjectUserName">xxxxx$</Data>
<Data Name="SubjectDomainName">HOME</Data>
<Data Name="SubjectLogonId">0x3e7</Data>
<Data Name="TargetUserSid">S-1-5-21-1619447833-111796513-3925427088-1000</Data>
<Data Name="TargetUserName">XXXXX</Data>
<Data Name="TargetDomainName">xxxx</Data>
<Data Name="TargetLogonId">0x69a0a</Data>
<Data Name="LogonType">2</Data>
<Data Name="LogonProcessName">User32 </Data>
<Data Name="AuthenticationPackageName">Negotiate</Data>
<Data Name="WorkstationName">xxxxx</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">0x40c</Data>
<Data Name="ProcessName">C:\Windows\System32\winlogon.exe</Data>
<Data Name="IpAddress">127.0.0.1</Data>
<Data Name="IpPort">0</Data>
</EventData>
</Event>

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 28/11/2013 8:01:03 AM
Event ID: 4672
Task Category: Special Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: xxxxx
Description:
Special privileges assigned to new logon.

Subject:
Security ID: XXXXXX\XXXXX
Account Name: XXXXXX
Account Domain: XXXXX
Logon ID: 0x69a0a

Privileges: SeSecurityPrivilege
SeTakeOwnershipPrivilege
SeLoadDriverPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeDebugPrivilege
SeSystemEnvironmentPrivilege
SeImpersonatePrivilege
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{22222}" />
<EventID>4672</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12548</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2013-11-27T21:01:03.239815000Z" />
<EventRecordID>6540</EventRecordID>
<Correlation />
<Execution ProcessID="1048" ThreadID="2224" />
<Channel>Security</Channel>
<Computer>xxxxx</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-21-1619447833-111796513-3925427088-1000</Data>
<Data Name="SubjectUserName">xxxxxx</Data>
<Data Name="SubjectDomainName">xxxx</Data>
<Data Name="SubjectLogonId">xxxx</Data>
<Data Name="PrivilegeList">SeSecurityPrivilege
SeTakeOwnershipPrivilege
SeLoadDriverPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeDebugPrivilege
SeSystemEnvironmentPrivilege
SeImpersonatePrivilege</Data>
</EventData>
</Event>

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 28/11/2013 8:00:59 AM
Event ID: 4624
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: xxxx
Description:
An account was successfully logged on.

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

Logon Type: 3

New Logon:
Security ID: ANONYMOUS LOGON
Account Name: ANONYMOUS LOGON
Account Domain: NT AUTHORITY
Logon ID: 0x56864
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x0
Process Name: -

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

Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): NTLM V1
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 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="{2222222}" />
<EventID>4624</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2013-11-27T21:00:59.182252600Z" />
<EventRecordID>6537</EventRecordID>
<Correlation />
<Execution ProcessID="1048" ThreadID="2224" />
<Channel>Security</Channel>
<Computer>xxxx</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-7</Data>
<Data Name="TargetUserName">ANONYMOUS LOGON</Data>
<Data Name="TargetDomainName">NT AUTHORITY</Data>
<Data Name="TargetLogonId">0x56864</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">
</Data>
<Data Name="LogonGuid">{00000000-0000-0000-0000-000000000000}</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">NTLM V1</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">-</Data>
<Data Name="IpPort">-</Data>
</EventData>
</Event>

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 28/11/2013 8:00:58 AM
Event ID: 5024
Task Category: Other System Events
Level: Information
Keywords: Audit Success
User: N/A
Computer: xxxx
Description:
The Windows Firewall service started successfully.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{2222222}" />
<EventID>5024</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12292</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2013-11-27T21:00:58.302239100Z" />
<EventRecordID>6536</EventRecordID>
<Correlation />
<Execution ProcessID="1048" ThreadID="1116" />
<Channel>Security</Channel>
<Computer>xxxx</Computer>
<Security />
</System>
<EventData>
</EventData>
</Event>

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 28/11/2013 8:00:58 AM
Event ID: 5033
Task Category: Other System Events
Level: Information
Keywords: Audit Success
User: N/A
Computer: xxxxx
Description:
The Windows Firewall Driver started successfully.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{2222222}" />
<EventID>5033</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12292</Task>
<Opcode>0</Opcode>
<Keywords>0x8020000000000000</Keywords>
<TimeCreated SystemTime="2013-11-27T21:00:58.204737600Z" />
<EventRecordID>6535</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="64" />
<Channel>Security</Channel>
<Computer>xxxxx</Computer>
<Security />
</System>
<EventData>
</EventData>
</Event>

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 28/11/2013 8:00:57 AM
Event ID: 4624
Task Category: Logon
Level: Information
Keywords: Audit Success
User: N/A
Computer: xxxxx
Description:
An account was successfully logged on.

Subject:
Security ID: SYSTEM
Account Name: xxxx$
Account Domain: HOME
Logon ID: 0x3e7

Logon Type: 5

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: 0x3d4
Process Name: C:\Windows\System32\services.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











 
Hi. I believe someone is trying to hack into your computer, using something that has been put in there. You can get more info here: http://www.bleepingcomputer.com/startups/Advapi-199.html If you click on the Removal link it will take you to maore inforamtion, as wel as something to use to remove it. I'll give you the link here: www.malwarebytes.org. Just use the Free version. I don't know what security stuff you are using, but I might want to rethink it and get something else.
 

ramond3

Honorable
Sep 12, 2013
70
0
10,660
9
start>computer>R click>properties>remote settings>remote>remote assistance (uncheck-allow remote assistance connections to this comp).under remote desktop (dont allow remote connections to this comp).Wireless network connection status>properties (uncheck-file and printer sharing for ms network,client for ms network)
 

Similar threads


TRENDING THREADS