How to clean up after a phishing attack that installed a backdoor trojan
A phishing message can cause serious damage even when it appears to contain a harmless document, invoice, or login page. If the payload installed a backdoor trojan, an attacker may have gained a way to run commands, steal information, download additional malware, or return after the initial infection has been removed.
Treat the computer and the accounts used on it as compromised. Avoid logging into banking, work, email, or cryptocurrency accounts from the affected device until it has been checked and cleaned. If the computer belongs to an organization, disconnect it from the network and notify the security team before making major changes.
The safest cleanup combines containment, evidence preservation, malware removal, password protection, and monitoring. Removing a suspicious file alone is rarely enough because backdoors can create scheduled tasks, alter startup settings, install browser extensions, or use stolen session cookies.
Isolate the infected computer
Disconnect the device from Wi-Fi and unplug its Ethernet cable. Disable Bluetooth if it is not needed, and remove external drives that were attached during or after the phishing incident. Network isolation can stop the trojan from receiving commands or sending additional data while you investigate.
Do not immediately delete every suspicious file or reset the computer if the incident may involve work systems, financial information, or sensitive documents. Preserve the phishing email, sender details, attachments, and screenshots where possible. Security teams may need this information to identify the entry point and determine whether other devices were targeted.
If the infected computer is used for business, contact the administrator from a separate, trusted device. Avoid using the compromised machine to change passwords because keystrokes, browser sessions, or new credentials could still be captured.
Protect accounts from a clean device
Use a trusted phone or computer to change the password for the email account associated with the phishing message. Then secure other important accounts, prioritizing password managers, banking, cloud storage, social networks, and workplace services. Use unique passwords and activate multifactor authentication with an authenticator app or hardware key when available.
Review recent sign-ins, active sessions, recovery addresses, forwarding rules, connected applications, and registered devices. Attackers may create an email forwarding rule or add a new authentication method so they can maintain access after the password changes. Revoke unfamiliar sessions and third-party permissions.
If financial details or identity documents were exposed, contact the relevant bank or service provider. Watch for unauthorized transactions, password-reset messages, new account alerts, and emails sent from your address that you did not write.
Remove the backdoor and related malware
Start with the operating system’s built-in security tools and update their malware definitions before scanning. Run a full scan rather than a quick scan. A second reputable on-demand scanner can help identify trojans, spyware, adware, and potentially unwanted programs missed by the first tool.
On Windows, inspect installed applications, startup entries, scheduled tasks, services, and browser extensions for unfamiliar additions. If the malware blocks security software or repeatedly returns, boot Windows into Safe Mode with networking disabled where possible, then perform scans and remove suspicious persistence mechanisms. On macOS, check Login Items, profiles, unfamiliar applications, browser extensions, and background processes.
Browser cleanup matters because phishing campaigns frequently install extensions or alter search settings after the main payload runs. A practical browser cleanup guide explains how to review Chrome, Firefox, and Edge for unwanted changes. Remove extensions you did not deliberately install and reset notification permissions for suspicious websites.
| Warning sign |
What it may indicate |
Recommended response |
| Unknown startup item or scheduled task |
Persistence after reboot |
Disable it, record its location, and scan the file |
| New browser extension or altered homepage |
Adware, credential theft, or traffic redirection |
Remove the extension and reset browser settings |
| Security tools suddenly disabled |
Tampering by the backdoor |
Re-enable protection and run an offline or Safe Mode scan |
| Repeated account alerts |
Stolen credentials or session tokens |
Change passwords from a clean device and revoke sessions |
| Files renamed, encrypted, or inaccessible |
A possible ransomware payload |
Disconnect the device and preserve affected files for analysis |
Check for persistence and stolen data
A clean scan does not prove that every attacker-controlled change has been removed. Review startup folders, scheduled tasks, services, browser policies, and recently installed software. Look for random filenames, unsigned programs in unusual directories, and entries that launch scripts or executables from temporary folders.
Examine browser history and download folders for suspicious sites, remote-access tools, archives, or scripts. Check whether the trojan may have accessed password stores, saved payment details, documents, or cryptocurrency wallets. If sensitive files were exposed, record what was stored on the device and inform the appropriate organizations.
Advanced users can review security logs and network connections, but unfamiliar system entries should not be deleted casually. Incorrect changes to services, the registry, or macOS configuration profiles can make the computer unstable. When persistence remains unclear, a complete operating system reinstall is often more reliable than repeated manual deletion.
Recover safely and monitor activity
Before restoring files, scan backups and external drives with a trusted security tool. Do not restore unknown executable files, cracked software, scripts, or browser installers from the compromised system. Personal documents should still be treated carefully if the attacker had time to modify or replace them.
Install operating system and application updates after cleanup, then enable automatic security updates. Replace outdated browsers, PDF readers, remote-access applications, and other software that may have helped the malicious file run. If a reinstall is necessary, download installation media from the official vendor and erase the system drive during setup.
Monitor accounts, email rules, login alerts, and financial statements for several weeks. Keep records of unusual activity, scan results, password changes, and devices that were reset. These details help identify delayed abuse and provide useful evidence if the incident needs to be reported.
Actions that reduce reinfection risk
Phishing defenses work best when technical controls support careful habits. Use a password manager to create unique credentials, enable multifactor authentication, and avoid opening unexpected attachments even when the message appears to come from a familiar company.
For additional practical guidance on safer browsing, updates, backups, and account protection, review these security tips. Build backups that are disconnected or protected from ordinary account access, and test restoration before an emergency occurs.
- Verify urgent payment, password, and document requests through a separate trusted channel.
- Keep browsers, operating systems, security tools, and office applications patched.
- Disable macros and script execution in documents unless they are required and verified.
- Use standard user accounts for everyday work instead of a local administrator account.
- Store recovery codes securely and review multifactor authentication methods regularly.
If the trojan installed a backdoor, assume that information may have been exposed until investigation shows otherwise. Isolate the device, secure accounts from a clean system, scan thoroughly, and reinstall when confidence in the cleanup is low. Begin those steps promptly so the attacker has less time to reuse stolen access or deploy another payload.