Malware Delivery, Execution, and Warning Signs
Learn how malware reaches devices, what causes it to run, and how to interpret possible warning signs.
Is Not the Same as
Is Not the Same as
is how malicious code reaches a device; is what causes it to run. These can be separate steps. For example, an email attachment or a file on a removable drive may bring malware to a device, but opening the file—or a software flaw processing it—may be what causes the code to run.
So, finding that a file arrived does not by itself show that malware executed or that the device was infected. A user action or another condition may still be needed, and security controls may block an attempt. Keep the two questions distinct: How could the code have arrived? and What, if anything, caused it to run?
Common Routes to a Device
Common Routes to a Device
Malware can reach a device through messages, websites, removable storage, or attacks that exploit software flaws. The route explains how it gets there; the later steps determine whether it runs.
Attachments and links
A phishing message may disguise a document, archive, PDF, or program as something expected. The source’s example is an unexpected “invoice” attachment that is actually an executable. Opening an attachment might run malware, prompt the user to enable active content, or exploit a flaw in the application handling the file.
A link in email, text, or a collaboration app might lead to a fake sign-in page, a malware download, or a page that attempts to exploit a browser or another application. In some cases, the user must download and open a file. In others, visiting a page may be enough if an application is vulnerable and unpatched. A familiar-looking message does not establish that its link is safe.
Websites and removable media
A starts with a visit to a site serving malicious content. The site may be attacker-controlled or compromised, and malicious advertising may direct visitors to harmful content. The attempt might rely on an outdated browser or plug-in, or on the visitor approving a download or prompt. Visiting a site does not always run code; the outcome depends on the circumstances.
An infected USB drive or other removable storage can carry malware between devices, even when a device is not connected to the internet. A file may run when opened, or a vulnerable or misconfigured system may process the drive’s contents. A drive that appears to belong to a colleague—or is found in a public place—is not automatically trustworthy.
Vulnerabilities and updates
If an attacker exploits a that permits code , malware may run without the user deliberately launching it. Security updates reduce exposure to known vulnerabilities, but cannot eliminate every risk. In practice, be cautious with unexpected files, links, and drives, and keep software updated.
Reading Warning Signs Carefully
Reading Warning Signs Carefully
Possible clues include an unexpected attachment or link, a file whose type does not match its name or icon, an unfamiliar download, or an unexpected prompt to enable content or install software. For defenders, an application unexpectedly launching another program, a new executable appearing after a click, or unusual outbound network activity soon afterward may also warrant investigation.
Treat these observations as clues, not proof. For example, an unexpected program launch after a click is a reason to investigate the sequence of events; it does not, by itself, show that the program was malicious. Legitimate software can also create unusual activity. Consider the observations in context rather than treating any single warning sign as definitive.
: An observation that may warrant investigation.