Seven malware patterns and the controls to check
Understand common malware labels and connect them to software sources, device protection, account access, alert ownership and incident response.

A security alert might call a threat a Trojan, spyware or fileless malware. These labels describe different aspects of an attack, so one incident can fit several of them. They don’t all represent newly discovered threats.
For a business owner, the useful question is what each label means for prevention, detection and the person responding. The Canadian Centre for Cyber Security’s malware guidance is a starting point for the terminology and basic protections.
1. Code that changes its appearance
Polymorphic malware changes how its code appears to make recognition harder. That doesn’t mean every changed copy is invisible to security software.
Ask IT whether your endpoint protection uses behaviour as well as known-file detection, and whether the relevant features are enabled. Microsoft’s behavioural blocking guidance describes capabilities that examine activity and process relationships. Confirm the product and plan you have before assuming coverage.
2. Fileless activity
Some attacks execute in memory or abuse legitimate tools and scripts. Looking only for an unfamiliar downloaded program can miss part of the activity.
Microsoft explains that fileless is a broad term: an attack can still involve files at another stage. Don’t assume a restart has cleaned the device.
Have IT review script controls, application restrictions and available endpoint evidence. Staff should report a website or message that asks them to paste commands into a terminal to fix a supposed problem.
3. Ransomware and data extortion
Ransomware can deny access to systems or files. An attacker may also steal information and threaten to release it. The Cyber Centre’s recovery guidance treats preparation and incident response as part of the defence.
Check whether backups are protected from the same access used for ordinary work and whether recovery has been tested. Follow the existing ransomware-readiness guide for the wider response plan.
4. Social engineering that delivers malware
Social engineering is a way to persuade someone to act. It isn’t a type of malware in itself. A fake invoice, update or support request can lead a person to install a malicious program.
Tell staff where to get software and how to check unusual requests. A familiar logo and polished wording don’t make a download safe.
5. Rootkits
A rootkit tries to hide an intruder’s access or activity. It can make a compromised system harder to inspect through ordinary tools.
Ask the incident-response owner how they would assess a device whose operating system can no longer be trusted. Don’t have staff repeatedly remove files or reset settings while an investigation is underway.
6. Spyware and information theft
Spyware collects information without permission. Information-stealing malware can target credentials and other data useful for accessing business services.
Device remediation may need to be paired with account containment. Use a trusted device for recovery actions, and have IT review affected sessions and credentials through the incident process. Removing the program doesn’t retrieve information already copied.
7. Trojans
A Trojan presents itself as something useful or harmless while carrying malicious behaviour. Installation packages and supposed utilities are examples of places to check the software’s source.
Install software only from sources IT has set up, and restrict unnecessary administrative access. Don’t rely on a filename or a familiar icon to decide whether an application is safe.
Turn the labels into an operational check
Pick representative devices and ask IT to demonstrate their protection status, recent updates and alert destination. Include a device that hasn’t reported recently and a staff member working away from the office.
Agree who reviews an alert, who can restrict access and how staff reach that person. Use a safe tabletop exercise or the test method your security vendor provides. Don’t download live malware to test the business.
Contact us if you need help reviewing endpoint controls and the handoff from a security alert to a response.


