Recognizing and reporting possible malware
Recognize device and account changes that need investigation, record useful details and hand suspected malware to IT without disrupting evidence.

A slow laptop or short battery life can have several causes. Malware is one possibility, but updates, a failing component or a busy application can produce similar symptoms. Some malicious activity produces no obvious symptom at all.
Staff don’t need to diagnose the threat. They need to recognize changes, report them and avoid actions that make the investigation harder.
Watch for changes you can’t explain
Report unexpected browser redirects, new extensions, repeated protection alerts or security settings that have changed. Files suddenly renamed or inaccessible, an unexpected ransom message, or an unknown remote-control session need prompt escalation.
Account activity matters too. Messages you didn’t send, unfamiliar sign-ins or changed recovery details can require account investigation alongside device checks.
The Cyber Centre’s malware guidance lists device, performance and account indicators. Treat them as reasons to investigate. On their own, they can’t confirm or rule out an infection.
Record the event without repeating it
Tell IT the device name, approximate time, exact warning and what you were doing just before it appeared. Mention a recently opened attachment, installed application or request to paste commands into a terminal.
Capture a warning if you can do so safely under your reporting process. Don’t reopen the attachment or revisit the site to reproduce the problem. Avoid putting passwords, client records or other sensitive information into an ordinary support message.
If a browser warning tells you to call a number or install a scanner, use your known IT contact instead. The warning itself may be an attempt to persuade you to grant access.
Let IT check protection and device evidence
Ask IT to confirm that the device is reporting, its protection is active and updates are current. The existence of an antivirus icon doesn’t show that alerts are being reviewed or that the device has checked in recently.
IT can compare installed applications, browser extensions, process activity and network evidence with the expected configuration. An unfamiliar process name or high resource use alone isn’t enough to justify deletion. It could be a legitimate system or management component.
The malware-pattern guide explains the terminology a responder may use. Keep staff instructions focused on reporting observations.
Use scans as part of the investigation
Run only the tools and scans IT asks for. Don’t disable existing protection or install a second product from a search advertisement. Avoid uploading a business file to a public scanning service unless the information owner and your response lead agree to it.
For supported Windows devices, Microsoft Defender Offline can scan outside the normal Windows environment. It restarts the device and has prerequisites, including x64 hardware and an enabled Windows Recovery Environment. If BitLocker is on, the restart may ask for the recovery key unless IT suspends it first. IT should confirm suitability, save work and check whether the scan completed.
An account or device can still be compromised after a scan finds nothing. Keep relevant alerts and observations available for the responder.
Escalate suspected compromise before cleanup
When the evidence suggests compromise, follow the incident plan. Stop sensitive work on the device and have the response lead direct isolation and further actions. Use a trusted device and communication route for recovery work.
Don’t copy everything to a connected backup drive, reset the computer or repeatedly restart it without direction. Those steps can affect evidence and recovery options. Account containment may also require reviewing sessions, tokens, forwarding and connected applications; changing a password alone can leave other access in place.
The cyberattack response guide covers the wider handoff. Reconnect and resume work when the responsible team has checked the result and says it’s safe.
Make reporting routine
Give staff a contact they can reach when work email is unavailable. Review one fictional alert with IT and check who receives it, who can act and what the staff member should do next.
Contact us to review device protection and the reporting process your team uses when something changes.


