Congruent Media Resourcing LLC v. Zimperium Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Congruent Media Resourcing LLC (Texas)
  • Defendant: Zimperium, Inc. (Delaware)
  • Plaintiff's Counsel: Ni, Wang & Massand, PLLC
• Case Identification: 3:26-cv-01920, N.D. Tex., 06/10/2026
• Venue Allegations: Venue is alleged to be proper in the Northern District of Texas because Defendant maintains a place of business in Dallas, Texas, within the district.
• Core Dispute: Plaintiff alleges that Defendant's Mobile Application Security Platform infringes a patent related to methods for creating secure software applications by injecting and integrating security intercepts.
• Technical Context: The technology addresses the need for enterprise-grade security on mobile applications, particularly in "Bring Your Own Device" (BYOD) environments, by "wrapping" existing applications with security features without modifying their source code.
• Key Procedural History: The complaint states that Congruent Media Resourcing LLC is the assignee of the patent-in-suit. No other procedural events, such as prior litigation or administrative challenges to the patent, are mentioned in the complaint.

Case Timeline

Date	Event
2010-01-01	Defendant Zimperium, Inc. founded
2011-10-10	'418 Patent Priority Date
2015-09-15	'418 Patent Issue Date
2026-06-10	Complaint Filing Date

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 9,135,418 - "System and Method for Creating Secure Applications"

• Patent Identification: United States Patent No. 9,135,418 ("the '418 Patent"), titled "System and Method for Creating Secure Applications," issued on September 15, 2015 Compl. ¶9

The Invention Explained

• Problem Addressed: The patent's background section describes the security risks that prevent enterprises from allowing corporate data and applications on employees' personal mobile devices, noting that many applications may contain malware and that IT departments have limited means to manage such devices '418 Patent, col. 1:21-41
• The Patented Solution: The invention provides a method for converting a standard "target application" into a secure one without accessing its source code '418 Patent, col. 1:65-67 This is achieved by imposing "intercepts" on the application, which are new or replacement instructions that can modify the application's behavior according to security policies '418 Patent, col. 1:54-64 The resulting secure application is then "repackaged" so that the intercepts become "physically inseparable" from the original files, creating an "immutable deployable entity" that resists tampering '418 Patent, col. 2:5-11
• Technical Importance: This method of "application wrapping" allows for the securitization of compiled applications, which removes the need for source code access or cooperation from the original developer, a significant advantage in enterprise security management Compl. ¶14 '418 Patent, col. 12:44-47

Key Claims at a Glance

• The complaint asserts independent claim 9 Compl. ¶17
• The essential elements of claim 9 are:
  • receiving a target application that is designed to interact with an operating system;
  • configuring the target application by imposing one or more intercepts on the target application, wherein the imposition of the intercepts converts the target application into a secure application that maintains the interaction with the operating system; and
  • repackaging the secure application such that the intercepts are integrated with the secure application and are inseparable from the secure application.
• The complaint does not explicitly reserve the right to assert other claims, focusing solely on claim 9 for direct infringement allegations Compl. ¶18

III. The Accused Instrumentality

Product Identification

• The accused instrumentality is the Zimperium Mobile Application Security Platform ("MASP") Compl. ¶18

Functionality and Market Context

• The complaint alleges that Zimperium MASP is a suite of in-app protection tools that leverage Runtime Application Self-Protection ("RASP") technology Compl. ¶19 Its key features are described as "No-Code App Shielding," "Code Obfuscation," and "Data Obfuscation," which are designed to safeguard applications without requiring additional code from developers Compl. ¶19, p. 6
• The platform is allegedly designed to be embedded into a target application to provide security without modifying the original development code Compl. ¶20 The complaint presents a marketing diagram from Zimperium illustrating a two-phase process of "DEVELOPMENT" and "RUN-TIME" security that results in the "Generation of new applications" Compl. p. 7

IV. Analysis of Infringement Allegations

'418 Patent Infringement Allegations

Claim Element (from Independent Claim 9)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
receiving a target application that is designed to interact with an operating system;	Zimperium MASP is allegedly "designed to be embedded into a target application" which interacts with the host operating system at the process and kernel interface level.	¶20	col. 1:44-46
configuring the target application by imposing one or more intercepts on the target application, wherein the imposition of the intercepts converts the target application into a secure application that maintains the interaction with the operating system;	Zimperium MASP allegedly "imposes one or more intercepts to convert a target application into a secure application." The complaint points to Zimperium's "zShield" product, which "embeds advanced security defenses into applications," and maintains interaction with the OS.	¶21	col. 1:54-57
and repackaging the secure application such that the intercepts are integrated with the secure application and are inseparable from the secure application.	Zimperium MASP allegedly "repackages an application by imposing intercepts during an application's launch," which combines code protection and other capabilities into features that "are integrated with the secure application and are inseparable."	¶22	col. 2:5-10

The complaint includes a screenshot with a callout stating "Imposing intercepts into target applications" to support its theory for the "configuring" step Compl. p. 9 To support the "inseparable" limitation, the complaint provides a visual from a third-party document describing the technology as a "self-contained" library where "User data is never exposed outside the application" Compl. p. 12

• Identified Points of Contention:
  • Scope Questions: A potential dispute may arise over the definition of "intercepts." The patent specification describes an intercept as potentially involving an "actual replacement of existing instruction" or a new instruction that "may interrupt program flow" '418 Patent, col. 1:66-2:3 The infringement analysis may turn on whether the Defendant's method of "embedding" security defenses via its "zShield" technology Compl. p. 9 meets this potentially narrow definition.
  • Technical Questions: A key question for the court will be the meaning of "inseparable." The '418 Patent specification explains that repackaging can result in an "immutable deployable entity" where intercepts are "physically inseparable from the original files" '418 Patent, col. 2:7-10 The complaint alleges that Zimperium's process makes the intercept an "inseparable part of a running process" Compl. ¶22 The case may turn on whether runtime inseparability is equivalent to the physical, file-level inseparability described in the patent's detailed description.

V. Key Claim Terms for Construction

• The Term: "intercepts"

  • Context and Importance: This term is the core technical mechanism for converting the target application into a secure one. The scope of this term will be critical, as the infringement case depends on whether Zimperium's security techniques qualify as "intercepts."
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent suggests a broad meaning by describing the process as "interposing system API calls to allow a secure framework to intercept and control application functions" '418 Patent, col. 21:43-49
    • Evidence for a Narrower Interpretation: The specification provides a more specific definition, stating an intercept "may be considered as an actual replacement of an existing instruction or a new instruction that may interrupt program flow and conditionally return control to the program flow" '418 Patent, col. 1:66-2:3 A defendant may argue this requires a direct modification of the application's instruction set.

• The Term: "inseparable"

  • Context and Importance: This term defines the required outcome of the "repackaging" step. The dispute may focus on whether the alleged inseparability of the accused product, described as being part of a "running process" Compl. ¶22, meets the claim's requirement.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The claim language itself simply requires that the intercepts "are inseparable from the secure application" without specifying the manner of inseparability '418 Patent, cl. 9
    • Evidence for a Narrower Interpretation: The specification elaborates that the repackaging process can make the intercepts "physically inseparable from the original files," resulting in an "immutable deployable entity" '418 Patent, col. 2:7-10 This language may support an argument that the term requires a static, file-level integration rather than just a runtime association.

VI. Other Allegations

• Indirect Infringement: The complaint alleges both induced and contributory infringement Compl. ¶23 It claims Defendant had knowledge of the '418 Patent and intended for its customers to infringe by providing the Zimperium MASP along with marketing materials, videos, and instructional guides that allegedly direct users to perform the infringing method Compl. ¶¶23-24
• Willful Infringement: The complaint does not use the term "willful." However, it alleges that Defendant has been on notice of its infringement "at least as of the date of the service of the original Complaint" and has continued its allegedly infringing conduct despite this knowledge Compl. ¶24 Compl. ¶25 This pleading structure establishes a basis for post-suit knowledge, which could support a future claim for enhanced damages for any ongoing infringement.

VII. Analyst's Conclusion: Key Questions for the Case

The resolution of this case may depend on the court's interpretation of two central issues:

• A core issue will be one of definitional scope: can the term "intercepts", which the patent specification suggests may involve the "actual replacement of existing instruction," be construed to cover the accused method of "embedding" a suite of security defenses into a target application?
• A key question will be one of technical equivalence: does the accused platform, which allegedly creates an "inseparable part of a running process," satisfy the claim limitation requiring intercepts to be "inseparable" from the secure application, particularly when the patent specification describes this as creating a "physically inseparable" and "immutable deployable entity" at the file level?