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

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is a Malware Signature?

A signature is a description precise enough to identify known malicious code and narrow enough to leave everything else alone. Both halves of that sentence cause trouble.

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

What Is a Malware Signature?

What Is a Malware Signature?

A malware signature is a pattern that identifies a known malicious file. In its simplest form it is a hash, a single value that matches one exact file and nothing else. In its most useful form it is a structured description of code, strings, and file characteristics that matches a whole family regardless of how each sample was built. The term covers both, which is why arguments about whether signatures are obsolete tend to be arguments about definitions.

The Main Types

Where Signatures Break

Attackers rebuild. Recompiling with a different compiler setting, changing a string, or running the output through a crypter produces a file that no hash in the world will match, and the service that does it costs less than a lunch. Polymorphic generation automates the problem by making every download unique.

Signatures are also silent on everything that is not a file. Fileless intrusions that run entirely in memory, abuse of legitimate remote management software, and attacks consisting only of valid credentials and normal administrative commands leave nothing for a file-matching engine to examine.

The False Positive Problem

A signature that is too generic is worse than no signature, because it damages systems that were never infected. On 21 April 2010, a McAfee definition update identified a core Windows system file as malicious on Windows XP Service Pack 3 and quarantined it, leaving machines in reboot loops across hospitals, police forces, and manufacturers. The pattern recurs across vendors: content updates ship faster than software updates, with correspondingly less testing, and they reach every endpoint at once.

The practical defence is operational rather than technical. Stage content updates to a pilot group where the product allows it, keep exclusion lists reviewed and minimal, and know in advance how to roll back a definition set on machines that will not boot. Write your own rules against a corpus of known-good software before deployment, since a rule that matches a popular library will find it everywhere.

What Replaced Them, and What Did Not

Modern endpoint products still carry signatures, because they are cheap, fast, and precise for the enormous volume of commodity malware that never changes. What has shifted is their position in the stack: they are now the first and least interesting layer, backed by behavioural detection that watches process relationships and actions, memory scanning that examines code after it has unpacked itself, machine learning classifiers trained on file structure, and reputation systems that weigh prevalence and age.

Behavioural rules written in formats such as Sigma, and endpoint detection content keyed to technique rather than content, are signatures in the broader sense. They describe what to look for. The difference is that they describe an action an attacker must take rather than a file an attacker can change, which is why a rule for credential dumping from process memory survives a repack and a hash does not.

For most organisations the right position is to stop asking whether signature detection is enough and start measuring coverage by technique. If your only detection for a given indicator of compromise is a file hash, the gap is already identified. At Privia Security, our endpoint security solutions combine signature, behavioural, and memory-based detection so that a new build of an old family does not walk through unnoticed.

FAQ – Frequently Asked Questions

Are Signature-Based Antivirus Products Obsolete?

No, but they are insufficient on their own. Signatures handle the large volume of unchanged commodity malware cheaply and with very few false positives, which keeps analyst time free for the rest. What they cannot do is detect new variants, fileless activity, or the abuse of legitimate tools, so they belong underneath behavioural and memory-based detection rather than in place of it.

How Quickly Do Attackers Defeat a New Signature?

Often within hours. Crypter services exist to test payloads against common products and rebuild until nothing detects them, a process that is largely automated. This is why detections built on behaviour matter more: an attacker can change file contents at negligible cost, but cannot avoid dumping credentials, establishing persistence, or contacting infrastructure without giving up the objective.

What Is the Difference Between a Signature and an Indicator of Compromise?

A signature is a detection pattern designed to be matched by a product against files or memory. An indicator of compromise is any observable suggesting a breach, including hashes, domains, IP addresses, file paths, and registry keys. Hashes belong to both categories, but most indicators are not signatures, and most useful signatures describe structure rather than a single value.

Can We Write Our Own Signatures?

Yes, and for targeted threats it is worthwhile. YARA is the usual choice: a rule can combine distinctive strings, byte patterns, and file structure, and can be run against files, memory, and many endpoint platforms. Test every rule against a large collection of legitimate software first, and anchor it with file type and size conditions to keep performance and accuracy acceptable.

Related Terms

You May Be Interested In These

How Do You Collect Cloud Compliance Evidence?

Cybersecurity Terms

17 November 2026

How Do You Collect Cloud Compliance Evidence?

Read More
What Is Cloud Forensics?

Cybersecurity Terms

17 November 2026

What Is Cloud Forensics?

Read More