← Latest papers
💻 computer science

Related Families, Not Label Errors: A Case Study of a Failure Mode in Open-World Malware Evaluation on BODMAS

This paper demonstrates that poor open-world malware detection performance on the BODMAS benchmark is caused not by labeling errors or detector flaws, but by the presence of closely related families in the training set that render held-out "novel" samples actually familiar to unsupervised novelty scoring methods.

Original authors: Vedant Shah, Fabio Di Troia

Published 2026-09-14
📖 5 min read🧠 Deep dive

Original authors: Vedant Shah, Fabio Di Troia

Original paper licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

In the digital world, security researchers build programs designed to act as sentinels, constantly scanning for malicious software that threatens computers. These programs are trained to recognize known threats, but the real challenge lies in the "open world," where entirely new types of malware appear every day. To test if these sentinels are truly ready for the unknown, researchers use a specific method: they hide a whole group of known bad software from the training program and then ask, "Can your system spot this new group as something it has never seen before?" If the system flags the hidden group as a stranger, it passes the test. This process assumes that the hidden group is genuinely unique and has no close relatives in the training data. If the hidden group is actually a cousin of a group the system already knows, the test breaks down, not because the system is weak, but because the question being asked is flawed.

A team of researchers recently investigated a puzzling failure in one of the most respected tests for malware detection, known as BODMAS. They found that when they removed a specific family of malware called berbew from the training data, the detection system failed spectacularly. Instead of flagging the hidden samples as new threats, the system confidently labeled them as safe, known software. The results were so poor that the system performed worse than random guessing. At first glance, this looked like a catastrophic failure of the detection technology. However, the researchers discovered that the fault lay not in the software's intelligence, but in the structure of the test itself. The hidden berbew family had a very close relative, called qukart, that remained in the training data. Because the two groups were so similar in their digital fingerprints, the system correctly recognized that the hidden samples belonged to a family it already knew, even though it didn't know the specific name of the hidden group. The test was penalizing the system for being accurate about the relationship between the two groups.

To prove this, the researchers conducted a controlled experiment. They removed both the berbew and qukart families from the training data at the same time, ensuring that no close relatives were left behind. When they ran the test again, the system's performance on the berbew samples skyrocketed from a failing score to near-perfect detection. This dramatic shift confirmed that the original failure was caused by the presence of a related family in the training set, not by a flaw in the detection algorithm. The researchers were careful to rule out other common explanations. They audited the entire dataset, checking thousands of pairs of malware families to see if any were actually duplicates with different names, which could have caused the confusion. They found no duplicates among the most suspicious pairs. They also examined the naming conventions used by antivirus vendors, which often group related malware under a single lineage name. They discovered that these names did not predict the problem; in one documented case, three families were considered part of the same lineage, but only two of them were actually close enough to confuse the system. The third was distinct, showing that relying on names alone would have merged the wrong groups and missed the real issue.

The study further revealed that this confusion was specific to the way the system measured "newness." The researchers tested several different mathematical approaches to spotting the unknown. They found that any method that compared a sample to a broad, global summary of all known software would fail when a close relative was present. These methods would see the hidden sample as normal because it was close to the known relative. However, a different approach, which compared a sample only to its nearest neighbors, performed better. It did not get the answer completely right, but it did not flip the result entirely, suggesting that looking at local details rather than a global average is a safer strategy when close relatives exist. The researchers also noted that a supervised system, which was allowed to use the family names during training, could separate the two groups effectively, proving that the labels were correct and the families were distinct, just very similar.

The core lesson from this work is that the way we test security software needs to change. Simply reporting a single average score for how well a system detects new threats hides these critical failures. The researchers argue that before declaring a test successful, we must first measure how closely related the hidden groups are to the groups used for training. If a hidden group has a close cousin in the training set, the test is not measuring the ability to find the truly unknown; it is measuring the ability to distinguish between very similar knowns. The solution is not to remove these related families from the test, as they represent realistic threats that security teams must handle. Instead, researchers should report the results separately for families that have close relatives and those that do not. This transparency ensures that a system is not unfairly punished for correctly identifying a known lineage, and it provides a clearer picture of where the technology truly stands. By documenting this specific failure mode and the steps taken to understand it, the researchers hope to prevent others from repeating the same mistakes and to encourage a more honest evaluation of how well our digital sentinels can truly see the unknown.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →