Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Hundreds of eventID 4625 being generated on server


  • Please log in to reply
No replies to this topic

#1 MF2015

MF2015

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:10:11 AM

Posted 07 October 2015 - 09:09 AM

Hello, I am getting hundreds of eventID 4625's being generated daily. This is a server for a business so I need to be careful about what I do regarding troubleshooting, turning things off, rebooting, etc. This is an SBS2011 server. 

 

Below is an example of one of the event logs. the user accountant and the domain and workstation CLARITYSERVER do not exist on this network. This is one example, in the hundreds of entries the usernames and domain names change, but they are always users and domains that do not exist. 

 

Does anyone know or have experience if this this kind of event indicative of a virus/malware on the server or more likely someone trying to hack in from the outside by using random users/domains?

 

Does anyone have any thoughts on how to track this down? Apologies in advance if this is in the wrong forum. 

 

 

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          10/7/2015 8:51:49 AM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      SERVERNAME.DOMAINNAME.local
Description:
An account failed to log on.
 
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
 
Logon Type: 3
 
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: accountant
Account Domain: CLARITYSERVER
 
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc000006a
 
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
 
Network Information:
Workstation Name: CLARITYSERVER
Source Network Address: -
Source Port: -
 
Detailed Authentication Information:
Logon Process: NtLmSsp 
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
 
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
 
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 was requested. The most common types are 2 (interactive) and 3 (network).
 
The Process Information fields indicate which account and process on the system requested the logon.
 
The Network Information 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.
- 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:
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2015-10-07T13:51:49.739564800Z" />
    <EventRecordID>274787883</EventRecordID>
    <Correlation />
    <Execution ProcessID="988" ThreadID="412" />
    <Channel>Security</Channel>
    <Computer>SERVERNAME.DOMAINNAME.local</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-0-0</Data>
    <Data Name="TargetUserName">accountant</Data>
    <Data Name="TargetDomainName">CLARITYSERVER</Data>
    <Data Name="Status">0xc000006d</Data>
    <Data Name="FailureReason">%%2313</Data>
    <Data Name="SubStatus">0xc000006a</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">NtLmSsp </Data>
    <Data Name="AuthenticationPackageName">NTLM</Data>
    <Data Name="WorkstationName">CLARITYSERVER</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</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>


BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users