Read the first chapter
The whole of chapter one, free. About 8 min. Turn the pages with the arrows, your keyboard, or a swipe.
Chapter 1
Signs Your PC Is Compromised
Read the Computer’s Warning Signs
Could an attacker be using your computer right now while the screen looks normal? A compromised system often gives small, observable clues before it produces an obvious failure: a new administrator account, a browser session you do not recognize, a process that returns after termination, or an outbound connection to an unfamiliar address.
These clues matter because malware, credential theft, and unauthorized access leave different traces. A slow computer alone proves little. A slow computer plus a new scheduled task and an unfamiliar login deserves immediate investigation. The goal is not to label every odd behavior as an attack. The goal is to recognize combinations of signals, record what you see, and decide whether to isolate the system before an attacker expands access.
After reading, you should be able to apply the Compromise Signal Checklist, distinguish weak symptoms from strong red flags, and collect first-pass evidence without destroying it. You will also know when a symptom supports a malware, credential-theft, or unauthorized-access hypothesis - and when it does not. Your practical takeaway: treat symptoms as evidence to test, not as a verdict.
Apply the Compromise Signal Checklist
The Compromise Signal Checklist groups warning signs into five areas: system activity, accounts, network connections, persistence, and browser or credential behavior. One signal may have an ordinary explanation. Several related signals that appear close together deserve prompt attention.
Start with the following checks:
1. Check for unexpected system activity. Open Task Manager on Windows or Activity Monitor on macOS and sort by processor, memory, and network use. Record the process name, path, publisher, and start time. A process named svchost.exe from C:\Windows\System32 differs materially from a similarly named executable running from C:\Users\Public\. The path and signer provide more useful evidence than the name alone.
2. Check accounts and sign-ins. Review local users, recent interactive logins, and remote sessions. On Windows, run whoami, query user, and net user. Review Security event logs for successful logons, especially logon type 10, which commonly indicates Remote Desktop Protocol (RDP) access. A new local administrator account or a successful login at 03:12 from an unfamiliar source deserves escalation.
3. Check active connections. Run netstat -ano on Windows or lsof -i -n -P on macOS and Linux. Match each established connection to a process identifier, then identify the owning process. An unfamiliar destination does not automatically indicate command-and-control traffic; software updates, cloud synchronization, and security tools also make outbound connections. The concern increases when an unsigned process maintains a connection after the user closes the related application.
4. Check persistence locations. Persistence allows code to start again after a reboot or user logon. Review Windows Task Scheduler, startup folders, services, and registry run keys. Microsoft Sysinternals Autoruns provides a consolidated view. Look for entries created recently, entries with missing publishers, and commands that launch PowerShell, a script interpreter, or an executable from a temporary directory. Preserve the entry before deleting it because it may explain how the compromise survives.
5. Check browser and credential signals. Look for unfamiliar extensions, changed search settings, unexpected proxy settings, saved passwords that appear accessed, and sessions that remain active after a password change. Credential theft often appears as account activity rather than local damage. Review the identity provider’s sign-in history, revoke unknown sessions, and change credentials from a known-clean device. Do not enter new credentials into the suspect computer until you contain it.
Use timing to connect the signals. If a user reports a new browser extension at 09:00, an unfamiliar sign-in at 09:08, and a PowerShell process at 09:10, record those events as one possible chain. Ask yourself: which observation is independently verifiable, and which one is only a user impression? That distinction keeps the investigation focused.
A useful first-pass decision rule is simple:
| Observed condition | Initial interpretation | Immediate action | |---|---|---| | One slow application, no other changes | Weak signal | Check resource use and recent software changes | | Unknown process with a valid publisher and expected path | Often legitimate | Verify the software and parent process | | Unknown process from a temporary or user-writable path | Stronger signal | Record details and investigate promptly | | New administrator account or unknown successful login | High-risk signal | Isolate the system and protect accounts | | Persistence entry plus outbound connection | High-risk combination | Preserve evidence, isolate, and escalate |
Do not terminate a suspicious process simply because it looks unfamiliar. First capture its path, command line, process identifier, parent process, hash if available, and network connections. Termination may stop immediate activity, but it can also remove volatile evidence and trigger a backup mechanism. The practical takeaway: compare signals across categories and preserve the facts that allow another analyst to reproduce your conclusion.
Work a Signal from Detection to Decision
Consider a Windows 11 workstation used for finance operations. At 08:40, the user reports that the browser opens a blank tab and the computer fan runs continuously. At 08:47, the user receives an identity-provider alert for a successful sign-in from an unfamiliar location. The symptoms alone do not prove compromise, but the combination of browser change, resource use, and unexpected authentication requires a controlled response.
Follow these steps:
1. Record the initial report at 08:50. Capture the user, hostname, logged-on account, local time, symptoms, and the identity alert. Do not ask the user to restart the computer. A restart may remove memory-resident evidence and alter timestamps.
2. Confirm the account event at 08:53. From the identity provider’s portal, verify the sign-in time, source address, application, device information, and authentication method. If the user did not initiate the sign-in, revoke active sessions and require a password reset from a known-clean device. The expected outcome is a documented account event and reduced risk of continued session abuse.
3. Isolate the workstation at 08:56. Use the endpoint detection and response (EDR) console to isolate the host while preserving its management channel, if the product supports that mode. If no EDR exists, disconnect the network cable or disable wireless. Do not power off the system unless active destruction or immediate safety concerns require it. Isolation prevents additional downloads and outbound theft while preserving volatile state.
4. Collect process details at 09:02. In Task Manager, identify the high-resource process. Suppose the process is update-check.exe, running from C:\Users\Public\Libraries\, unsigned, with a PowerShell parent. Record the process identifier, command line, file path, file creation time, and hash. The expected outcome is a repeatable record that another analyst can verify.
5. Check connections at 09:08. Run netstat -ano and match the process identifier to an established connection on TCP port 443. Record the destination address, local port, and timestamp. Port 443 carries normal encrypted web traffic, so the port alone does not establish malicious activity. The unusual file path, unsigned binary, PowerShell parent, and persistent connection form the meaningful combination.
6. Check persistence at 09:15. Run Autoruns and inspect scheduled tasks, services, startup entries, and registry run keys. Suppose a task named UpdateHealth launches the same executable every hour under the user account. Export the task definition and record its creation time before disabling it. The expected outcome is a documented persistence mechanism and a controlled containment action.
7. Preserve and escalate at 09:25. Export relevant Windows event logs, the identity-provider sign-in record, EDR timeline, browser extension list, and collected file hash. Send the package to the incident-response case with timestamps in Coordinated Universal Time (UTC) and the workstation’s time zone. Do not upload the suspicious file to a public scanning service if it may contain sensitive business data; use an approved internal analysis path.
8. Verify the immediate result at 09:40. Confirm that the identity provider shows no unknown active sessions, the EDR reports the host as isolated, and the suspicious task no longer launches. These checks confirm containment, not recovery. The system still requires deeper investigation, credential review, and likely rebuilding if the attacker obtained administrator access.
The checklist below captures the minimum response for a similar first report:
Quick checklist
• Record the symptom, hostname, user, and exact times. - Verify unexpected sign-ins in the identity-provider logs. - Isolate the computer without restarting when safe. - Capture process path, publisher, command line, process identifier, and hash. - Match suspicious processes to active network connections. - Review scheduled tasks, services, startup entries, and browser extensions. - Revoke unknown sessions and reset exposed credentials from a clean device. - Preserve logs and exported evidence before removing artifacts. - Document what you checked, what you found, and what remains unknown.
The expected outcome is not a clean-looking desktop. It is a defensible decision: benign, suspicious and contained, or confirmed compromise requiring recovery work.
Avoid Misreading the Evidence
Treating slowness as proof of malware
High processor use can result from an operating-system update, browser tab, backup job, or security scan. Malware becomes more plausible when high use connects to an unsigned process, an unusual path, persistence, or an unexplained network connection.
Do this: record the process path, publisher, parent process, start time, and network activity. Compare those details with installed software and scheduled maintenance.
Not this: delete the highest-consuming file immediately. Deletion removes a lead and may leave the actual persistence mechanism active.
Assuming an unfamiliar connection identifies the attacker
Geolocation and reputation tools provide context, not proof. Content-delivery networks, cloud services, and shared hosting can make a legitimate application appear unfamiliar. Attackers also use common cloud providers.
Do this: map the connection to a process, command line, certificate or publisher, DNS history where available, and repeated timing. Check whether the application normally uses that service.
Not this: block one address and declare the system clean. A malicious process may use another address, domain, or encrypted channel after the block.
Changing passwords on the suspect computer
Credential theft can involve browser cookies, password stores, keylogging, or active sessions. Changing a password from the same compromised host can expose the replacement credential immediately.
Do this: isolate the computer, use a known-clean device, revoke active sessions, reset the affected account, and review multifactor-authentication changes and recovery methods.
Not this: rely only on a password reset. Check mailbox rules, browser extensions, delegated access, newly registered authentication devices, and recent sign-ins because unauthorized access may persist through sessions or account changes.
A final edge case deserves attention: a legitimate administrator may create a task, service, or remote session during maintenance. Confirm the change with the change record and the administrator before classifying it as malicious. If no one can explain it, preserve it and continue investigating rather than silently removing it.
The Compromise Signal Checklist works because it forces separate observations into a timed, testable record. Symptoms start the investigation; correlated evidence determines the response. Once you can recognize those signals, the next decisions - what to isolate, what to preserve, and what to rebuild - become much clearer.
End of chapter one. 15 more chapters and about 29,941 words in the full book.
Swipe or use the arrows to turn the page
What's inside: 16 chapters
- 1. Signs Your PC Is Compromised
- 2. Threat Model for Your Environment
- 3. What EDR and Antivirus Actually Do
- 4. Configuring EDR Alerting Rules
- 5. Suspicious Processes Triage Workflow
- 6. Accounts and Logins That Don’t Belong
- 7. Connections, DNS, and Beaconing Clues
- 8. Persistence Mechanisms to Hunt
- 9. Browser Compromise and Malicious Extensions
- 10. Credential Theft Indicators and Checks
- 11. Logs You Must Collect First
- 12. Evidence Preservation Without Breaking Things
- 13. Containment: Isolate, Quarantine, and Block
- 14. Commands and Tools for Live Triage
- 15. Rebuild vs Repair and Malware Removal
- 16. Verify the Fix and Monitor Post-Incident
About this book
"Is My Computer Hacked?" is a how-to guide book by David Simpson with 16 chapters and approximately 29,941 words. Detect, investigate, contain, recover, and monitor a compromised computer.
This book was created using Inkfluence AI, an AI-powered book generation platform that helps authors write, design, and publish complete books. It was made with the AI Ebook Generator.
Frequently Asked Questions
What is "Is My Computer Hacked?" about?
Detect, investigate, contain, recover, and monitor a compromised computer
How many chapters are in "Is My Computer Hacked?"?
The book contains 16 chapters and approximately 29,941 words. Topics covered include Signs Your PC Is Compromised, Threat Model for Your Environment, What EDR and Antivirus Actually Do, Configuring EDR Alerting Rules, and more.
Who wrote "Is My Computer Hacked?"?
This book was written by David Simpson and created using Inkfluence AI, an AI book generation platform that helps authors write, design, and publish books.
How can I create a similar how-to guide book?
You can create your own how-to guide book using Inkfluence AI. Describe your idea, choose your style, and the AI writes the full book for you. It's free to start.
Write your own how-to guide book with AI
Describe your idea and Inkfluence writes the whole thing. Free to start.
Start writingCreated with Inkfluence AI