Last Updated: May 31, 2026

Patent: 10,034,938


✉ Email this page to a colleague

« Back to Dashboard


Summary for Patent: 10,034,938
Title:Method for treating melanoma using a herpes simplex virus and an immune checkpoint inhibitor
Abstract: The invention relates to methods of treating melanoma using a herpes simplex virus in combination with an immune checkpoint inhibitor.
Inventor(s): Vanderwalde; Ari (Memphis, TN), Shabooti; Mohamed (Agoura Hills, CA)
Assignee: Amgen Inc. (Thousand Oaks, CA)
Application Number:14/424,424
Patent Litigation and PTAB cases: See patent lawsuits and PTAB cases for patent 10,034,938
Patent Claims:see list of patent claims
Patent landscape, scope, and claims summary:

US Patent 10,034,938: What the Claims Actually Cover and How Crowded the Landscape Is

US Patent 10,034,938 is directed to combination immunotherapy for advanced melanoma (stages IIIb to IV) using an oncolytic herpes simplex virus engineered to be ICP34.5- and ICP47-deficient and to express human GM-CSF, in combination with an immune checkpoint inhibitor that is an anti-PD-1 or anti-CTLA-4 antibody. The strongest claim set ties the engineered HSV to T-VEC (talimogene laherparepvec)-type genetics and treatment patterns, and locks the immunotherapy partner to specific commercially relevant checkpoint antibodies, with dosing and sequencing language in dependent claims.

What are the core independent claim themes?

Claim 1: method with engineered HSV + anti-PD-1/anti-CTLA-4

Claim 1 is the broad method claim. It requires four technical elements:

  • Patient population: “stages IIIb to IV melanoma”
  • Immune checkpoint inhibitor: an anti-PD-1 antibody or anti-CTLA-4 antibody
  • Herpes simplex virus engineering:
    • herpes simplex virus lacks a functional ICP34.5 gene
    • herpes simplex virus lacks a functional ICP47 gene
    • herpes simplex virus comprises a gene encoding human GM-CSF
  • Administration concept: HSV is administered as part of the combination (sequencing is added in dependent claims)

Claim 1 is broad on the checkpoint side (covers both PD-1 and CTLA-4 antibodies) and broad on administration (no dosing schedule in claim 1 itself).

Claim 2: kit containing engineered HSV + instructions for combination treatment

Claim 2 mirrors Claim 1 in kit form. It requires:

  • A HSV with ICP34.5- / ICP47- / GM-CSF profile
  • A package insert or label with directions to treat stages IIIb to IV melanoma using:
    • the engineered HSV + an anti-PD-1 or anti-CTLA-4 antibody

Claim 2 is important because kit claims can be used to control distribution even when method practice by a clinic is less cleanly attributable.

What do the dependent claims narrow to?

Checkpoint antibody identity and antibody class

  • Claim 4: checkpoint antibodies are IgG
  • Claim 5: anti-CTLA-4 is ipilimumab
  • Claim 8: anti-PD-1 antibody is selected from nivolumab, lambrolizumab, CT-011, AMP-224
  • Claims 14, 17, 18: repeat IgG and checkpoint choice in kit context

This means the patent set does not just cover “anti-PD-1/anti-CTLA-4” generically. It also includes explicit enumerations of commercial/late-stage candidates and clinical-stage molecules.

HSV identity (T-VEC lock-in)

  • Claim 7: HSV is talimogene laherparepvec
  • Claims 11 and 12: HSV is talimogene laherparepvec and anti-CTLA-4 is ipilimumab
  • Claims 16 and 18: T-VEC + anti-PD-1 selected from lambrolizumab or nivolumab
  • Claims 13 and 9: specify tumor site injection targets (injectable cutaneous, subcutaneous, and nodal tumors)

This structure creates two layers:

  1. A chemistry/genetic specification layer (ICP34.5-/ICP47-/GM-CSF) that can cover engineered HSV variants meeting the profile.
  2. A product identity layer (T-VEC) that can make enforcement easier by tying to a known commercial product.

Sequencing requirement

  • Claim 6: HSV precedes the administration of the anti-PD-1 or anti-CTLA-4 antibody

Sequencing language can materially affect infringement analysis against protocols that administer checkpoint first, or that administer concurrently.

Dosing and schedule lock-in (the high-friction claim)

Claim 3 is the most operationally specific claim. It requires:

  • HSV: Talimogene laherparepvec-type genetics (ICP34.5-/ICP47-/GM-CSF) and includes:
    • Intratumoral injection
    • Dose schedule:
    • up to 4.0 mL at 10^6 PFU/mL at day 1 of week 1
    • up to 4.0 mL at 10^8 PFU/mL at day 1 of week 4
    • then every 2 weeks thereafter until complete response
  • Anti-CTLA-4: 3 mg/kg IV every 3 weeks, for 4 infusions
    • starting after the third dose of HSV

Claim 9 is a kit analog that repeats substantially the same operational dosing and injection-target language, plus the CTLA-4 schedule.

Manufacturing claim

  • Claim 10: “method of manufacturing the kit of claim 2”

A manufacturing claim can support downstream control (labeling/packaging/combination preparation) but it also tends to be narrower in practice because actual “manufacturing of a kit” is fact-dependent.

What is the claim coverage in plain technical terms?

US 10,034,938’s coverage centers on a very particular HSV engineering profile that is widely associated with T‑VEC. The checkpoint combination is framed to include anti-PD-1 or anti-CTLA-4, then dependent claims narrow to:

  • ipilimumab (anti-CTLA-4)
  • nivolumab/lambrolizumab (anti-PD-1) and also enumerated clinical candidates (CT-011, AMP-224)

The enforcement posture is strongest where all of these elements align:

  • patient population: stage IIIb to IV melanoma
  • HSV: ICP34.5-, ICP47- and GM-CSF
  • treatment structure: HSV-first sequencing and/or dosing schedule
  • checkpoint pairing: ipilimumab or the enumerated PD-1 antibodies

How does the dependent claim scaffold map to likely infringement scenarios?

Scenario A: clinic uses T-VEC + ipilimumab with a similar sequence

  • High match to Claims 1, 6, 7, 11, 12, 3 (depending on whether full dosing language is used)
  • Moderate match to Claims 2, 9 if kit labeling matches and includes the specified schedule

Scenario B: clinic uses HSV engineered differently from ICP34.5/ICP47 deletion

  • Low match unless the HSV still lacks functional ICP34.5 and ICP47 and includes human GM-CSF

Scenario C: HSV injection site differs (non-injectable or different lesion classes)

  • Claims 13 and 9 specify injectable cutaneous/subcutaneous/nodal tumors, so variants could avoid those dependent claims while still potentially triggering broader claim 1/2.

Scenario D: PD-1 antibody partner is an unlisted anti-PD-1

  • Claim 1/2 still cover “anti-PD-1 antibody” in general.
  • Avoidance is possible if the partner is not a PD-1 antibody (for example, an antibody that targets a different checkpoint).

Where is the patent landscape most crowded? (Freedom-to-operate pressure points)

The landscape for T‑VEC-like oncolytic HSV plus checkpoint blockade is crowded because:

  • T‑VEC’s genetic deletions (ICP34.5 and ICP47) and GM‑CSF expression are a known oncolytic HSV platform.
  • Checkpoint combinations for melanoma are widely claimed across multiple patent families (each partner drug has its own IP around dosing, indications, combinations, and formulations).
  • Kit and label claims like Claims 2 and 9 can extend control over distribution and use instructions.

Key crowding vectors

  1. HSV platform IP: genetic-engineering claims and method claims tied to ICP34.5/ICP47 deletion and GM‑CSF expression.
  2. Combination immunotherapy IP: combination method claims for melanoma involving checkpoint antibodies and oncolytic HSVs.
  3. Product identity: where independent claims are generic but dependent claims point to T‑VEC, commercial enforcement becomes cleaner.
  4. Dose/schedule and sequencing: Claimed timing can carve out protocol-specific exclusivities and create inter-protocol infringement ambiguity.

Critical analysis: where the claims are strong versus where they are vulnerable

Strengths

  • Genetic definition is crisp: “lacks functional ICP34.5,” “lacks functional ICP47,” and “comprises GM‑CSF.” This is concrete and testable in HSV characterization.
  • Checkpoint scope is broad in independent claims: Claim 1 covers anti-PD-1 or anti-CTLA-4 without naming a single antibody.
  • Operational specificity exists: Claim 3 and Claim 9 lock dosing and scheduling for HSV and ipilimumab, which increases enforceability against clinics following the specific regimen.
  • Product tie-in: dependent claims that name T‑VEC reduce ambiguity for enforcement and licensing.

Vulnerabilities

  • Biological equivalence risk: if an HSV is engineered to achieve similar functional outcomes but does not literally lack functional ICP34.5/ICP47, claim 1 may be avoided. This creates a design-around path based on HSV genetics.
  • Protocol dependence: Claim 3 uses explicit dosing units, injection timing, and “until complete response.” Even if a clinic uses the same concept, deviations in dosing schedule or starting infusion timing can weaken infringement of the dependent claims.
  • Indication boundaries: the claims are limited to stages IIIb to IV melanoma. Using similar therapies in earlier stages or in different melanoma populations can avoid these claims.
  • Antibody substitution risk: Claim 5 is ipilimumab and Claim 8 is a list of PD-1 antibodies. Even though claim 1 still covers “anti-PD-1,” other claim sets for those specific antibodies may be more heavily litigated in the broader landscape, changing practical risk allocation.

How investors should treat the patent in a diligence model

US 10,034,938 functions as a combination-control patent built on a platform HSV and paired with checkpoint immunotherapy. Its value depends on:

  • whether competitors’ HSV constructs match the ICP34.5/ICP47/GM‑CSF profile, and
  • whether competitors’ combination protocols match:
    • HSV-first sequencing (Claim 6),
    • ipilimumab dosing/schedule (Claim 3),
    • and kit labeling directions (Claims 2 and 9).

A realistic diligence conclusion is that the patent creates high licensing friction for any program that intends to run T‑VEC-like HSV with checkpoint inhibitors in stage IIIb to IV melanoma using a similar regimen.

Claim-to-landscape pressure map

Claim element Enforceability lever Common design-around vector
ICP34.5 deletion (no functional ICP34.5) Testable genetic requirement Alternative HSV engineering that alters ICP34.5 status
ICP47 deletion (no functional ICP47) Testable genetic requirement Alternative ICP47 modification
GM-CSF expression Testable transgene requirement Different cytokine payload or expression pattern
Anti-PD-1 or anti-CTLA-4 scope Broad independent claim Use non-PD-1/non-CTLA-4 checkpoint mechanism
Stage IIIb to IV restriction Limits indication Use in other melanoma stages/populations
Sequencing (HSV precedes) Protocol-specific Administer checkpoint before or concurrently
Dose schedule and “until complete response” Protocol-specific Deviate dosing frequency or start time

Key Takeaways

  • US 10,034,938 claims a method and kit for stage IIIb to IV melanoma using an HSV that is ICP34.5- and ICP47-deficient and expresses human GM-CSF, combined with anti-PD-1 or anti-CTLA-4 antibodies.
  • The patent’s practical strength comes from dependent claims that name T‑VEC and ipilimumab, and from Claim 3/9 that recite a specific intratumoral HSV dosing schedule and ipilimumab IV schedule with sequencing logic.
  • Freedom-to-operate risk concentrates on programs that use:
    • T‑VEC-like genetics (or literal equivalents that meet the “functional” deletion criteria), and
    • checkpoint combination protocols that preserve the HSV-first and regimen timing elements.

FAQs

1) Does Claim 1 require ipilimumab?

No. Claim 1 covers an anti-PD-1 antibody or an anti-CTLA-4 antibody. Ipilimumab is specified in Claim 5 and in T‑VEC + ipilimumab dependent claims.

2) Is T‑VEC required for infringement?

Not for Claim 1, which is defined by HSV genetics (ICP34.5/ICP47/GM‑CSF). T‑VEC appears in dependent claims like Claim 7 and Claims 11-13, 16, 18.

3) Which claim is most operationally constraining?

Claim 3. It recites intratumoral dosing volumes, PFU concentrations by week, dosing frequency, and the ipilimumab schedule and its start relative to HSV dose number.

4) Are kit claims part of the enforcement strategy?

Yes. Claim 2 and dependent Claim 9 cover a kit with label/package directions to treat stage IIIb to IV melanoma using the combination.

5) What is the main design-around path suggested by the claim language?

Alter the HSV so it does not meet the strict engineering requirements (functional ICP34.5 or functional ICP47) or swap the checkpoint mechanism away from anti-PD-1/anti-CTLA-4, or change regimen timing so dependent schedule/sequencing claims are not met.


References

[1] US Patent 10,034,938. (n.d.). Patent claims text as provided in prompt.

More… ↓

⤷  Start Trial

Details for Patent 10,034,938

Applicant Tradename Biologic Ingredient Dosage Form BLA Approval Date Patent No. Expiredate
Bristol-myers Squibb Company YERVOY ipilimumab Injection 125377 March 25, 2011 10,034,938 2033-08-30
Amgen Inc. IMLYGIC talimogene laherparepvec For Injection 125518 October 27, 2015 10,034,938 2033-08-30
Bristol-myers Squibb Company OPDIVO nivolumab Injection 125554 December 22, 2014 10,034,938 2033-08-30
Bristol-myers Squibb Company OPDIVO nivolumab Injection 125554 October 04, 2017 10,034,938 2033-08-30
Bristol-myers Squibb Company OPDIVO nivolumab Injection 125554 August 27, 2021 10,034,938 2033-08-30
>Applicant >Tradename >Biologic Ingredient >Dosage Form >BLA >Approval Date >Patent No. >Expiredate

International Patent Family for US Patent 10,034,938

Country Patent Number Estimated Expiration
World Intellectual Property Organization (WIPO) 2014036412 ⤷  Start Trial
United States of America 2019060452 ⤷  Start Trial
United States of America 2015202290 ⤷  Start Trial
Portugal 3381942 ⤷  Start Trial
South Korea 20210008155 ⤷  Start Trial
South Korea 20150047512 ⤷  Start Trial
>Country >Patent Number >Estimated Expiration

Make Better Decisions: Try a trial or see plans & pricing

Drugs may be covered by multiple patents or regulatory protections. All trademarks and applicant names are the property of their respective owners or licensors. Although great care is taken in the proper and correct provision of this service, thinkBiotech LLC does not accept any responsibility for possible consequences of errors or omissions in the provided data. The data presented herein is for information purposes only. There is no warranty that the data contained herein is error free. We do not provide individual investment advice. This service is not registered with any financial regulatory agency. The information we publish is educational only and based on our opinions plus our models. By using DrugPatentWatch you acknowledge that we do not provide personalized recommendations or advice. thinkBiotech performs no independent verification of facts as provided by public sources nor are attempts made to provide legal or investing advice. Any reliance on data provided herein is done solely at the discretion of the user. Users of this service are advised to seek professional advice and independent confirmation before considering acting on any of the provided information. thinkBiotech LLC reserves the right to amend, extend or withdraw any part or all of the offered service without notice.