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

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Static Malware Analysis?

Static analysis examines a sample without running it, reading structure, strings, and code. It is quick, safe, and covers paths that execution would never take.

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

What Is Static Malware Analysis?

What Is Static Malware Analysis?

Static malware analysis is the examination of a file without executing it. You read what it is made of: headers, sections, imported functions, embedded resources, readable strings, and, with a disassembler, the instructions themselves. Nothing runs, so nothing can escape, and the analysis covers code paths that would never be reached in a single execution.

Its weakness is equally clear. Packing and encryption mean the file on disk may contain almost nothing of the real program, which is why static work alone rarely finishes the job.

A Practical Order of Work

Working in sequence saves time, because most samples are identified long before the disassembler is needed.

  1. Hash and reputation. Calculate SHA-256 and check whether it is already documented. Known commodity malware with published reporting does not usually need further analysis; take the indicators and go hunting.
  2. True file type. Identify the format from its header rather than its extension. A document claiming to be a PDF that begins with MZ is already the answer.
  3. Strings. Extract both ASCII and UTF-16 text. Domains, file paths, registry keys, command lines, and error messages often appear in plain view. A sample with almost no readable strings is itself a finding.
  4. File structure. For a Windows executable, examine the compile timestamp, section names, section entropy, the import table, exports, resources, and any digital signature. A stolen or expired certificate is important, and a signature that fails to verify is more interesting than none at all.
  5. Capability assessment. Imports suggest intent: cryptography and file enumeration functions together point towards ransomware, while process injection and keyboard hook functions suggest something else. Tools that map imports and byte patterns to capabilities give a usable summary in seconds.
  6. Disassembly. Open the binary in Ghidra or an equivalent and read the entry point and the functions reached from it. This is where cost rises sharply, so it should answer a question you have already framed.

Documents, Scripts, and Managed Code

Not every sample is a compiled executable, and the non-executable cases are often easier. Office documents are archives or structured storage files whose macro streams can be extracted and read directly, including the compiled p-code when the readable source has been stripped. PDFs can be parsed to list their objects and any embedded JavaScript or launch actions. Scripts need deobfuscation rather than disassembly, usually by unwrapping encoding layers until the final command appears. .NET assemblies and Android applications decompile close to their original source, so a sample written in those languages can be read almost as written unless it has been protected.

When the File Tells You Nothing

Several findings together indicate that the sample is packed: section entropy above roughly 7.2, an import table containing only a handful of loader functions, raw section sizes much smaller than their virtual sizes, and three readable strings where there should be hundreds. At that point static analysis has reached its boundary. The usual move is to let the sample unpack itself under dynamic analysis, dump the reconstructed code from memory, and repeat the static steps on that dump, which frequently reads like an ordinary binary.

Treating the two as alternatives is a common mistake. They are stages of the same process, and the hand-off between them is where most findings emerge.

Handling Samples Safely

Static analysis does not execute the file, but accidents do. Keep samples in password-protected archives so no scanner quarantines your only copy, strip or neutralise the extension on disk, and work on a machine that is not joined to the corporate domain. Remember that analysis tools parse hostile input and have their own vulnerabilities; several document and archive parsers have been exploited through malicious files. Record provenance for every sample, because an incident may end in a claim, a dispute, or a regulatory submission, and a sample containing stolen records remains personal data regardless of why you are holding it.

The output should be usable the same day: hashes, strings worth hunting for, extracted configuration, and YARA rules written from genuinely distinctive content rather than from compiler boilerplate. At Privia Security, our digital forensic incident response services fold sample analysis into the investigation so that what is learned from one file is immediately searched for across the estate.

FAQ – Frequently Asked Questions

Is Static Analysis Safe to Perform on My Own Machine?

Safer than execution, but not risk-free. The file is never run, yet your tools parse attacker-controlled input, and parsers for documents and archives have been exploited before. A careless double-click is also always possible. Work on an isolated machine that is not domain-joined, keep samples in password-protected archives, and rename extensions so nothing launches accidentally.

What Can Static Analysis Find That Running the Sample Cannot?

Code that did not execute. A sample may check the date, the domain, or the keyboard layout and take a different path, so a single run reveals one behaviour out of several. Reading the code exposes conditional branches, unused capabilities, embedded configuration, and triggers that depend on conditions your lab does not satisfy, which matters when assessing what the malware would have done elsewhere.

Which Tools Do I Need to Start?

Very few. A hashing utility, a file type identifier, a strings extractor that handles both ASCII and wide characters, a PE parser for headers and entropy, and Ghidra for disassembly will cover most work. Add document-specific tools for macro and PDF extraction. Everything listed is freely available, so the real investment is practice rather than licensing.

How Do I Know When to Stop Static Analysis?

When the next finding stops changing a decision. If you already know the family, the persistence mechanism, and the network destinations, further reading is research rather than response. Stop early too when the file is packed and shows almost nothing, since detonating it and analysing the memory dump will recover more in ten minutes than hours of reading the stub.

Related Terms

You May Be Interested In These

What Is Voice Cloning Fraud?

Cybersecurity Terms

17 November 2026

What Is Voice Cloning Fraud?

Read More
What Is KVKK, the Turkish Data Protection Law?

Cybersecurity Terms

17 November 2026

What Is KVKK, the Turkish Data Protection Law?

Read More
What Are Azure Managed Identities?

Cybersecurity Terms

17 November 2026

What Are Azure Managed Identities?

Read More