Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Malware Analysis?

Malware analysis answers the questions an alert cannot: what the sample was built to do, what it already did, and what the rest of the estate should now be searched for.

Illustration for the cybersecurity term Malware Analysis
Home / Blog / Cybersecurity Terms / What Is Malware Analysis?
17 November 2026

What Is Malware Analysis?

What Is Malware Analysis?

Malware analysis is the structured examination of a malicious file or memory artefact to establish what it does, how it does it, and how to find every other instance of it. It is a response activity, not a research hobby: the output is meant to change containment decisions, detection content, and the scope of an investigation while those things are still in flux.

The work is usually described as four stages of increasing cost. Most samples never reach the fourth, and deciding where to stop is as much a skill as the analysis itself.

Stage One: Triage

Before anything is opened, establish what the file is and whether anyone has seen it before. Hash it and check reputation services, identify the true file type rather than trusting the extension, and note size, compile timestamp, and any digital signature. A known commodity family with existing public reporting rarely justifies deeper work; the sensible move is to take the published indicators and start hunting.

A sample that nobody has seen, that is signed with a certificate belonging to one of your suppliers, or that appeared on a server rather than a workstation deserves the opposite treatment. Those are the cases where the time spent pays for itself.

Stage Two and Three: Static and Dynamic

Static analysis reads the sample at rest: strings, imports, resources, section entropy, and embedded objects. It is fast, safe, and complete in the sense that it covers code that may never run on a given machine. It is also the stage that packing and obfuscation are designed to defeat.

Dynamic analysis runs the sample in an instrumented, isolated environment and records behaviour: processes, files, registry changes, and network traffic. Encryption has to unwind at runtime, so this stage recovers what static work could not, at the cost of seeing only the path the sample chose on that occasion.

Treating them as a sequence misses the point. Analysts alternate: a dynamic run produces a memory dump of unpacked code, static work on that dump reveals a configuration decryption routine, and a targeted debugger session extracts the configuration. The hand-off between stages is where most of the value appears.

Stage Four: Reverse Engineering

Full reverse engineering means reading the disassembled or decompiled code to understand logic that neither of the previous stages exposed. It answers specific, expensive questions: which files were selected for exfiltration, whether the encryption implementation has a weakness, what the kill switch condition is, and whether the sample was tailored to your environment. It takes days rather than hours, so it needs a question worth asking before it starts.

What the Output Should Look Like

A report that ends with a description has failed. Useful analysis produces artefacts other people put to work the same day:

Handling and Evidence

Samples are evidence as well as objects of study. Record where each one came from, who handled it, and what was done to it, because an incident may end in litigation, an insurance claim, or a regulatory submission. Store them in password-protected archives so scanners do not quarantine your only copy. Consider before uploading anything to a public service: files submitted there may be shared, and a document containing client data remains personal data regardless of the malware attached to it. A sample that names your organisation also tells an attacker, watching submissions, that the campaign has been noticed.

Most organisations do not need a full analysis capability in-house. What they do need is a decision rule for when a sample must be analysed, and a relationship in place before the day they need one. At Privia Security, our investigation and incident response services include sample analysis as part of containment, with the indicators fed straight back into the hunt.

FAQ – Frequently Asked Questions

When Should We Analyse a Sample Rather Than Just Remove It?

Analyse when the answer changes what you do next. That applies to unknown samples with no public reporting, anything found on a server or in a privileged context, signed files from a supplier, and any detection where you cannot establish what ran before you intervened. For well-documented commodity malware cleanly quarantined on one workstation, published indicators are usually enough.

Do We Need Reverse Engineers on Staff?

Rarely. Most organisations get sufficient value from triage and automated sandbox reports, supported by a specialist retained for the few cases that justify deeper work. What matters more is having the decision rule written down, the samples preserved properly, and the relationship arranged in advance, because finding a reverse engineer during an incident wastes the hours that count.

Is Submitting a File to VirusTotal Safe?

It is a disclosure, so judge it case by case. Uploads may be shared with other subscribers, meaning a document with client data, an internal utility, or a targeted sample referencing your organisation should not go there. Attackers monitor public submissions, and an upload can reveal that their campaign has been discovered. Hash lookups carry far less risk than file uploads.

How Long Does Malware Analysis Take?

Triage takes minutes and automated detonation adds perhaps half an hour. Combined static and dynamic work by an analyst typically runs from a few hours to a day, which covers the great majority of cases. Full reverse engineering of a packed, obfuscated sample takes days to weeks, so it should be commissioned against a specific question rather than started by default.

Related Terms

You May Be Interested In These

What Is Health Data Anonymisation?

Cybersecurity Terms

17 November 2026

What Is Health Data Anonymisation?

Read More
What Is Indirect Prompt Injection?

Cybersecurity Terms

17 November 2026

What Is Indirect Prompt Injection?

Read More
What Is LDAP Injection?

Cybersecurity Terms

17 November 2026

What Is LDAP Injection?

Read More