Skip to content
Home » Breach & Incident Response » 7 Signs Your Windows Server May Have Been Compromised

7 Signs Your Windows Server May Have Been Compromised

Infographic titled “7 Signs Your Windows Server May Have Been Compromised” showing a server under attack with alerts, unusual logins, and suspicious activity indicators.

Attackers rarely announce themselves. Mandiant’s M-Trends 2025 report, covering incidents it investigated in 2024, puts the global median time between an intrusion and its discovery at 11 days. When the victim found it themselves the median was 10 days; when an outside party had to tell them, it was 26. That is plenty of time to copy client files, plant a way back in, or prepare ransomware.

Here are seven signs that your Windows server may have been compromised, with the event ID or check for each one. This post is about an attacker who may already be inside. If you want to spot someone still trying the door, read how to tell if someone is trying to break into your server. Run the commands below in PowerShell as administrator; the Security log is not readable otherwise.

1. User accounts you did not create

One of the first things many attackers do is create an account of their own, or add an existing one to Administrators, so they keep a way in after you change the password they stole. An unfamiliar account with admin rights is a serious red flag.

Where to look: event 4720 (account created) and 4732 (member added to a local group such as Administrators) in the Security log. To see who is an administrator right now:

Get-LocalGroupMember -Group Administrators
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4720,4732} -MaxEvents 50 -ErrorAction SilentlyContinue | Format-List TimeCreated, Id, Message

2. Remote sign-ins at odd hours

If the office works 9:30 to 7 and the server shows a Remote Desktop sign-in at 3 a.m. on a Sunday, someone needs to explain it. Attackers like hours when nobody is watching. In tax season late work is normal, so check who it was before you panic, but do check.

Where to look: event 4624 with logon type 10 (Remote Desktop). This lists recent ones with the account and source address:

Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4624} -MaxEvents 5000 -ErrorAction SilentlyContinue | Where-Object { $_.Properties[8].Value -eq 10 } | Select-Object TimeCreated, @{n='User';e={$_.Properties[5].Value}}, @{n='SourceIP';e={$_.Properties[18].Value}}

3. The server is slow or the processor is busy for no reason

Compromised servers are often put to work: mining cryptocurrency, attacking other targets or packing up stolen data. If the server is sluggish and nobody is running anything heavy, open Task Manager (Details tab, sort by CPU) and look for processes you cannot explain.

Where to look: there is no single event ID for this. Task Manager and Resource Monitor (resmon) are the tools. A miner usually arrives as a service or scheduled task, so sign 5 below often finds it.

4. Antivirus, firewall or logging switched off

Attackers know that security tools can catch them, so they turn them off. If Defender’s real-time protection is off, the firewall is off, its rules have changed, or the logs have been cleared, do not assume a glitch. Security software rarely switches itself off.

Where to look:

  • Microsoft Defender: event 5001 (real-time protection disabled) in the Microsoft Defender Antivirus operational log, and Get-MpComputerStatus | Format-List RealTimeProtectionEnabled, AntivirusEnabled, AntivirusSignatureLastUpdated for the current state.
  • Windows Firewall: Get-NetFirewallProfile -PolicyStore ActiveStore | Format-Table Name, Enabled for the current state, and events 4946 to 4950 (rule added, changed or deleted, or a firewall setting changed) in the Security log. Those events appear only if “Audit MPSSVC Rule-Level Policy Change” is on; our recommended audit policy turns it on.
  • Cleared logs: event 1102 (Security log cleared) and 104 (System or another log cleared). Clearing the log is a classic way of covering tracks.

5. Services or scheduled tasks you did not set up

Remote-access tools, keyloggers and miners need to start again after a reboot, so attackers install them as services or scheduled tasks. Anything unfamiliar deserves a question to your IT vendor.

Where to look: event 7045 in the System log (a new service was installed, logged by default), 4697 in the Security log (the same, if “Audit Security System Extension” is on; our recommended audit policy turns it on) and 4698 (scheduled task created, if “Audit Other Object Access Events” is on). To list them directly:

Get-WinEvent -FilterHashtable @{LogName='System'; Id=7045} -MaxEvents 20 -ErrorAction SilentlyContinue | Format-List TimeCreated, Message
Get-ScheduledTask | Where-Object { $_.TaskPath -notlike '\Microsoft\*' } | Format-Table TaskName, TaskPath, State

Remote-support tools such as AnyDesk or UltraViewer also install services. If one appears that nobody in the office installed, treat it as sign 1 and sign 5 together.

6. Files encrypted, renamed or missing

Files with strange extensions, documents that will not open and a ransom note are the loudest sign of all: ransomware has already run. Quieter versions matter too, such as folders moved, Tally data or a database with gaps, or files deleted that nobody remembers deleting.

Where to look: by default Windows does not log who opened, changed or deleted a file. File auditing has to be switched on in advance, so for this sign your evidence is usually the files themselves and your backups. Ransomware is the reason backups need one copy offline or immutable, and a restore you have actually tested.

7. Unusual outbound traffic

A server talks to a predictable set of places: Windows Update, your antivirus, your accounting software’s licence server. Large uploads to unknown addresses, a router showing heavy traffic at night, or your ISP warning that your IP is sending spam all point to a server being used by someone else. A server that sends spam can also land the firm in legal trouble; see your server got hacked and is sending spam.

Where to look: outbound connections are not logged by default. Resource Monitor’s Network tab shows which process is talking to which address right now, and the router’s traffic page shows volume over time.

What to do if you see these signs

  1. Disconnect, do not switch off. Pull the network cable or disable the network adapter. Leave the server running unless you cannot disconnect it, because memory and running processes are evidence.
  2. Write down what you saw and when: the time, the account names, the addresses, screenshots of any ransom note.
  3. Call your IT vendor or an incident-response firm. Do not reset everything yourself first; you may wipe the trail they need.
  4. Report to CERT-In within six hours of noticing. Under CERT-In’s Directions of 28 April 2022, incidents such as unauthorised access, data breaches and ransomware must be reported within six hours. Email [email protected] or call 1800-11-4949. An initial report is enough; details can follow. If money was stolen, also call 1930 or report at cybercrime.gov.in.

From May 2027, the DPDP Act and Rules will also require you to tell the Data Protection Board and each affected person about a personal data breach. This is a summary, not legal advice. Our incident response guide for small businesses walks through the full sequence.

Getting told instead of having to look

Signs 1, 2, 4 and 5 all leave entries in the event logs, which means they can be watched. Prixl Warden reads those logs on the server and emails you when it sees new accounts or admin-group changes, sign-ins outside your working hours, admin sign-ins, new services or scheduled tasks, a cleared audit log, or the firewall being switched off or its rules changed. Its security audit also checks that Defender is running. Signs 3, 6 and 7 are not in the logs by default, and Warden does not watch them, so keep an eye on them yourself and keep tested backups.

Warden can watch for the log-based signs for you. Start your 30-day free trial.

Related reading

Leave a Reply

Your email address will not be published. Required fields are marked *