Remove Trojan and Spyware Infections
Legacy cleanup guide based on archive reports of trojans, spyware, and suspicious system behavior, with careful notes on what still applies.
Hub page
Computer Security Troubleshooting Archive
Curated legacy archive for malware cleanup, privacy issues, suspicious traffic, and other computer security troubleshooting threads.
Intro
The computer-security archive is tighter than the original site. The strongest material here is practical: malware cleanup cases, repeated connection attempts that worried users, and site-access problems where the question was whether to block an address or restore access.
This hub avoids turning the archive into a generic security publication. It keeps the threads that still help explain symptoms, cleanup decisions, and common misunderstandings around traffic, pings, blocking, and older protection tools.
Strongest Curated Guides
Start with the guides in this cluster: Remove Trojan and Spyware Infections, Suspicious Connection Attempts and Ping Issues, and Block an IP Address or Unblock Your Connection.
Suspicious Connection Attempts and Ping Issues
Legacy guide to repeated connection attempts, odd ping behavior, and related network symptoms reported in the WebSecurity.mobi archive.
Block an IP Address or Unblock Your Connection
Legacy troubleshooting guide for blocking unwanted IP access or getting an address unblocked when a site or service shuts you out.
Selected Legacy Threads
Can't Enter Sites Like Microsoft and Others
Legacy computer-help thread about being unable to reach certain sites while others still load, with preserved troubleshooting context.
Import Your IPSec Policy Question
Legacy security thread about importing an IPSec policy and the problems that can follow. Preserved for archive context.
Internet Privacy Issues
Legacy archive thread on older internet privacy concerns, preserved for context with the original problem statement and troubleshooting notes.
Archive Context
Some security software, malware names, and cleanup steps in the archive are obviously dated. They can still show how the problem presented itself, but they should not be treated as a complete modern incident-response process.
What still matters is the reasoning: verify the symptom first, separate real compromise signs from normal network behavior, and use older tool-specific advice only when the page clearly labels it as legacy context.