Malware and ransomware: the difference
Understand how ransomware fits within malware, why stolen information needs separate attention and what staff should report before recovery starts.

Malware is a broad term for malicious software. Ransomware is one type of malware, so the two names don’t describe separate, competing threats.
The distinction helps explain an alert, but staff don’t need to diagnose an attack before reporting it. Unusual account activity, a protection warning or inaccessible files should reach the person responsible for incident response promptly.
Malware describes harmful software
Malware can steal information, monitor activity, damage files or misuse a device. Terms such as virus, worm, Trojan and spyware describe aspects of its operation. One attack can involve several kinds of malicious activity.
The Cyber Centre’s malware guidance covers common types and routes into a system, including malicious downloads, attachments, removable media and exploited vulnerabilities.
For a business, the practical questions are what the attacker accessed, what changed and whether other systems or accounts are affected. A label on one file doesn’t answer those questions.
Our malware-pattern guide connects more detailed terminology to the controls IT should check.
Ransomware denies access and demands payment
Ransomware can encrypt files or make a system unusable while demanding money to restore access. An attacker may also copy information and threaten to publish it. Data extortion can occur without encryption.
The Cyber Centre’s ransomware guidance addresses both disruption and theft. A readable backup can help restore operations, but it can’t retrieve information already taken by an attacker.
Don’t assume a ransom message is the beginning of the incident. Have the response team investigate earlier access and affected systems. Payment doesn’t guarantee usable recovery or that stolen information will be deleted.
Report symptoms without diagnosing them
A slow device or crashing application can have ordinary technical causes. A ransom note or sudden change to many files is more specific, but staff should report what they observe without trying to classify it themselves.
Useful details include:
- the device and account involved;
- the time and wording of an alert;
- what was opened, downloaded or installed shortly beforehand;
- which files or tasks are affected;
- any unusual sign-ins or messages sent from the account.
Use the reporting route in your incident plan. Don’t forward a suspect attachment to colleagues or upload confidential files to a public scanning service. A screenshot can preserve an error message if you can take it safely and send it through that same route.
Let the response owner direct containment
Stop the affected work and contact IT through a trusted channel. If work email may be affected, use the alternative contact recorded in the plan.
Follow the business’s instructions for isolating a device from networks. Don’t keep reconnecting it to test whether the problem has gone away. Let the response team decide whether to leave it powered on, shut it down or take other steps; evidence and operational needs affect that decision.
Avoid deleting suspect files, reinstalling software or running several cleanup tools before the team assesses the situation. Use a trusted device for any instructed account-recovery actions. After a password reset, ask IT to check active sessions, connected applications and other access too.
Recovery includes accounts and business decisions
The response team should establish scope, preserve relevant evidence, address the entry route and agree when restored systems can return to use. Business owners need to check that recovered records and applications support real work.
The privacy lead should assess exposed personal information and applicable reporting or notification duties. A malware alert isn’t automatically a reportable privacy breach, and successful restoration doesn’t settle that assessment.
Use the cyberattack-response guide for the wider handoff and the ransomware-readiness exercise to practise it safely.
Contact us to review endpoint protection, recovery coverage and the route from a staff report to an incident response.


