Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.

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.
Working in sequence saves time, because most samples are identified long before the disassembler is needed.
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.
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.
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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.