Background
Vir2us, Inc. holds patents on antivirus “containerization” technology that isolates potentially malicious files in a virtual safe room. After suing Invincea, Inc. for patent infringement, the parties settled in July 2016 with an agreement granting Invincea a worldwide patent license in exchange for royalty payments on sales of defined “Container Products” — four specifically named products plus “natural evolutions and derivations” of them. When Sophos, Inc. acquired Invincea in 2017, it integrated Invincea’s machine-learning source code (but not its containerization code) into several Sophos products, then discontinued all X by Invincea products entirely.
Vir2us sued Invincea and Sophos in 2019 under diversity jurisdiction, alleging breach of the settlement agreement for failure to report sales and pay royalties on certain Sophos products (including Sophos Intercept X and Sandstorm). A prior appeal to the Fourth Circuit had already resolved that the disputed Sophos products did not fall within the first part of the Container Products definition — the exhaustive named list — because shared source code alone does not make a product one of the four enumerated accused container products. The case was remanded to decide whether the disputed Sophos products qualified as “natural evolutions and derivations” of the named products.
On remand before Judge Jamar K. Walker, both parties moved for summary judgment on the “natural evolutions and derivations” question. Vir2us argued only the “derivations” prong, contending that shared Cynomix machine-learning source code files made the Sophos products derivations of the named container products. The district court granted summary judgment to Sophos, finding that a “derivation” must employ containerization technology — which the disputed Sophos products undisputedly do not. Vir2us appealed.
The Court’s Holding
The Fourth Circuit affirmed per curiam, holding that the disputed Sophos products are not “derivations” of the accused container products as a matter of law under the agreement’s plain language. Drawing on dictionary definitions from Webster’s, Merriam-Webster, the Oxford English Dictionary, and Black’s Law Dictionary, the court concluded that a “derivation” requires a direct, sequential lineage — the later product must have originated from or been produced from the earlier one. Merely sharing some source code is insufficient to establish that relationship.
The court identified two independent gaps in Vir2us’s record evidence. First, versions of the disputed Sophos products existed before Invincea’s code was ever integrated into them, meaning the accused container products were not their originating source. Second, Vir2us produced no evidence that Sophos physically extracted the shared Cynomix code from any of the accused container products rather than obtaining it through other means after acquiring Invincea — and deposition testimony from a Sophos integration employee affirmatively suggested the latter. Shared source code that was deactivated in the accused container products (and thus played no functional role in them) cannot render a later product that activates that code a “derivation” of the former.
The court also grounded its conclusion in contractual context. The defined term “Container Products” is oriented entirely around containerization technology, and the first part of the definition’s four named products all employed containerization. The “natural evolutions and derivations” clause, read as part of a definition about container products, logically extends only to future products that similarly employ containerization. Because the disputed Sophos products use only machine-learning functionality and not containerization, they fall outside the royalty provision.
Key Takeaways
- Shared source code between two products does not, without more, establish a “derivation” relationship sufficient to trigger royalty obligations under a patent license agreement — the later product must trace direct lineage from the earlier one.
- When interpreting a defined contractual term, courts will read “evolutions and derivations” expansions in light of the entire definition’s subject matter; a “Container Products” definition anchors derivations to containerization technology even if the agreement’s text does not say so explicitly.
- A party claiming royalties under a “natural evolutions and derivations” clause bears the burden of affirmatively showing lineage — including how and from where code was obtained — not merely identifying common code across products.
- The parties’ omission of existing products (Invincea’s Detect and Prevent) from the named list at the time of contracting carries interpretive weight against expanding the definition to cover products that use only the non-containerization features of shared source code.
Why It Matters
This decision offers important guidance on how courts interpret “natural evolutions and derivations” clauses — a common drafting device in patent settlement agreements intended to prevent royalty evasion through product rebranding or minor modification. The Fourth Circuit makes clear that such clauses require genuine product lineage traceable to the named originating products, not merely technical commonality in underlying code. Licensors relying on these provisions to capture successor or derivative products must be prepared to show a direct developmental relationship, not just shared components.
For technology companies negotiating patent settlements, the case underscores the importance of precisely defining the scope of royalty-bearing products at the time of contracting. Broad “evolutions and derivations” language will be construed in light of the named products’ core functionality — meaning that acquirers who selectively integrate only the non-patented features of licensed technology may successfully argue they have stepped outside the royalty obligation entirely.