Threat library

Trojans: investigate an alert and its scope

Investigate a Trojan alert by file origin, execution and recorded actions, assess additional components and remote access, and choose supported cleanup and recovery.

A Trojan alert is a reason to investigate the exact item, whether it ran and what actions completed. The category describes a deceptive program; it does not tell you whether that particular file stole information, installed another component or enabled remote control. Start with the security product’s evidence rather than the most alarming interpretation of its name.

This guide covers personal Windows PCs and Macs. Use the Trojan glossary for the definition and the beginner flow for urgent ongoing access or file damage. On work or school equipment, preserve the finding and use IT’s incident process before changing required software or submitting files externally.

Verify the finding independently

Open the installed security app through the normal app menu, rather than a button in the warning. Record its full detection name, affected path or item, time, action and completion state. A page listing “Trojans found” is not a scan record from your installed product. Use pop-up diagnosis if the source is unclear.

For Microsoft Defender, Protection History distinguishes action-needed, quarantined, blocked and incomplete-remediation entries. Expand the relevant card when authorized. Microsoft documents a two-week retention window, so preserve important details promptly rather than assuming the list is a permanent incident archive. Other products have their own history and action labels.

Finding contextUseful questionAppropriate next step
A download was blocked before known executionDid the recorded action finish, and was anything else opened?Leave the item isolated and review the entry route
A finding names a compressed archiveWas anything extracted or executed from it?Assess that history without extracting it again
A program ran before a later detectionWhat permissions and subsequent activity are known?Assess the device and potential exposure
Remediation is incomplete or the finding returnsWhich action or component remains unresolved?Follow product instructions and obtain qualified help
A familiar application is disputedIs this exact copy from the intended publisher?Investigate provenance without allowing the item

A clean follow-up scan answers what that check found in its scope. It cannot retrospectively establish that no earlier execution or disclosure occurred. Preserve the original action status as well: a later clean result does not explain why an earlier remediation remained incomplete. Keep the history and uncertainty together rather than replacing the incident record with a screenshot of zero detections.

Reconstruct arrival, execution and permissions

Write a short timeline: how the file arrived, what you opened, whether you approved an installation or elevated access, and when the alert appeared. Include an attachment, unofficial download, browser prompt or remote-support interaction if relevant. Receiving a file is distinct from running it; opening an advertised app successfully does not establish that the copy was trustworthy.

Microsoft’s Trojan overview describes legitimate-looking names and installation either by a person or by other malware. Its capability examples include additional downloads, information collection and attacker control. These are investigation branches, not a checklist of actions proven by every Trojan alert.

Use safer-download checks for publisher and release context, and attachment guidance for message-delivered items. A signature or familiar icon provides limited identity information; it does not settle the behavior of an entire installation chain. Never rerun a suspicious installer, re-enable blocked content or paste the original deceptive command to reconstruct the event.

Investigate the behavior identified by the product

Read the detecting vendor’s explanation for the exact finding. Microsoft’s classification criteria distinguish downloaders, droppers, backdoors and other behaviors. Names and categories provide leads; vendors can describe related activity differently. A dramatic label is not evidence of every possible payload.

For an additional-component lead, preserve related findings and times. A downloader needs assessment of what it retrieved; a dropper may carry other code. Removing the original downloaded file does not establish that all later components were removed. The downloader and dropper explanations help interpret those terms without executing the suspect item.

If credible evidence points to data theft, use infostealer exposure assessment to prioritize accounts, sessions and relevant secrets. If it points to continuing control, treat the access as part of the incident. If files were changed or locked, use ransomware investigation to preserve recovery options. Do not force an unexplained performance problem into one of those branches without supporting evidence.

Distinguish a malicious program from abused remote support

A legitimate remote-support product can be used by someone you did not intend to authorize. Its presence alone does not establish a remote access Trojan, and its authenticity does not make an abusive session harmless. Record whether you requested support, how the person contacted you and what permissions or actions you approved.

Microsoft’s April 2026 helpdesk-impersonation research describes deceptive Teams contact and remote assistance used to obtain control, followed by further execution. It is a documented Windows intrusion pattern, not proof that your installed Quick Assist or Teams is malicious or that every support session has that outcome.

When unexpected remote control is active, use urgent triage and trusted support rather than continuing sensitive work while collecting a perfect screenshot. A session ending does not identify everything installed or accessed during it. IT can assess approved tooling on a managed device; personal-device investigation needs the actual controller and timeline rather than bulk removal of familiar remote-access applications.

Complete supported remediation and account recovery

Leave uncertain items quarantined or blocked. Follow the existing product’s supported action, then confirm completion instead of assuming the click succeeded. On Windows, the scan guide covers product status and follow-up checks. On Mac, use the platform guide and its supported controls. Windows-only scanner procedures do not become Mac instructions because the threat name is the same.

For a disputed finding, follow the false-positive process before allowing anything. Independent publisher confirmation and detecting-vendor review concern the exact item. Public file or indicator services require a privacy decision; private documents, installers containing business material and full logs should not be uploaded as a routine prerequisite.

Use another trusted device for affected account work. Google’s compromised-account instructions illustrate reviewing activity, devices, recovery details and unwanted account changes. The appropriate provider controls the actual recovery. Follow the account guide for prioritization, and record credential replacement separately from revoking sessions or application access.

Verify the scope before returning to sensitive use

Check completed product actions and the absence of recurring findings under ordinary use. Record any item that returns after restart, another application’s launch or sign-in. A recurring detection needs assessment of the controller and scope; repeatedly deleting one file is not an explanation.

Use recovery verification for unresolved changes, protection status and rebuilding decisions. If continued control, additional payloads or important data exposure cannot be assessed, get qualified help before relying on the device for sensitive work. Preserve wanted-data and recovery requirements rather than performing an unplanned reset.

The final record should distinguish what arrived, what is known to have executed, completed remediation and outstanding device or account questions. This article is researched guidance. No Trojan was executed, private sample submitted, remote session initiated or independent detection test performed to prepare it.

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy