Last Updated: July 14, 2026

Patent: 10,005,779


✉ Email this page to a colleague

« Back to Dashboard


Summary for Patent: 10,005,779
Title:1\',4\'-thio nucleosides for the treatment of HCV
Abstract: Provided herein are compounds, compositions and methods for the treatment of Flaviviridae infections, including HCV infections. In certain embodiments, compounds and compositions of nucleoside derivatives are disclosed, which can be administered either alone or in combination with other anti-viral agents. In certain embodiments, the compounds are 1\',4\'-thio nucleoside compounds which display remarkable efficacy and bioavailability for the treatment of, for example, HCV infection in a human. In certain embodiments, the compounds are of Formula 3001: ##STR00001## or a pharmaceutically acceptable salt, solvate, stereoisomeric form, tautomeric form, or polymorphic form thereof; wherein Base, R.sup.A, R.sup.B, W, X, Y, and Z are as described herein.
Inventor(s): Dukhan; David (Saint Gely du Fesc, FR), Gosselin; Gilles (Montpellier, FR), Dousson; Cyril B. (Canet, FR)
Assignee: IDENIX PHARMACEUTICALS LLC (Cambridge, MA)
Application Number:14/296,122
Patent Claims:see list of patent claims
Patent landscape, scope, and claims summary:

Executive summary

  • US 10,005,779 claims a broad genus of hepatitis C virus (HCV) antiviral compounds defined by Formula (3001) (and dependent narrowing to additional sub-formulas), including pharmaceutically acceptable salts/solvates/polymorphs. The claims also cover oral pharmaceutical compositions and treatment methods for HCV infection, including combinations with other direct-acting antivirals (DAAs) and/or interferons.
  • The claim set is primarily chemical-genus and functional-infringement breadth. The scope is driven by large “Markush” style variable lists for substituents (Base, W, X, Y, Z and substituent groups), and by inclusion of amino-acid residue/derivative moieties via N-linked or O-linked groups.
  • Without the patent’s specification, claim constructions, file history, and the rest of the asserted claim set beyond what you supplied, a complete claim-by-claim infringement map and a definitive freedom-to-operate (FTO) assessment against known competitors cannot be produced.

H1: US Patent 10,005,779 claims for Formula 3001 HCV antiviral compounds, compositions, and treatment methods


What is claimed in US 10,005,779 (Formula 3001) for hepatitis C treatment?

Core independent claim (as provided): Claim 1 recites a compound “according to Formula 3001” (or salt/solvate/tautomer/polymorph) with a set of structural variables:

  • Base: a defined heterobase structure (and tautomeric forms).
  • W: S or O.
  • R4, R5, R6, R7: substituent-type variables with limited choices (mostly H, hydroxyl, alkoxyl, amino/alkylamino, halogen, alkyl).
  • X and Y: independently selected from H, alkoxy/thioalkoxy/amino substituent forms, or N-linked/O-linked amino-acid residue/derivatives with further sub-definition.
  • Amino-acid residue integration:
    • N-linked: “--NR^X-G(S_C)--C(O)-Q^1
    • O-linked: “--OC(O)G(S_C)-Q” or “--O-C(O)-G(S_C)-NH-Q^2
    • G: C1–C2 alkylene.
    • S_C: side chain of a naturally occurring amino acid or from a long enumerated list (including multiple protected/functional derivatives).
  • Q / Q1 / Q2: sulfur/amine/alkoxyl type substituents, with restricted R/Y choices.
  • Z: hydrogen/hydroxyl/halo, with a ring-closure alternative where Y and Z together form a six-membered heterocycle containing a single divalent --O--.

Key breadth features

  1. Large Markush-style substitution space: X and Y independently vary across multiple functional classes and linkages.
  2. Two “geometry” regimes: (i) standard Z as H/OH/halo; (ii) alternative Y–Z cyclization into an O-containing six-membered heterocycle.
  3. Amino-acid residue scaffolding: inclusion of amino-acid side chains and residue derivatives expands chemical diversity while staying within the claim’s binding pattern for the variable “amino acid” handle.

How broad is the “Markush” scope (Base, W, X/Y/Z and substituent permissiveness)?

Claim-driven breadth indicators

  • Base: restricted to specific heterocyclic “Base” structures (not fully spelled out in text, but the claim provides dedicated Base-dependent claims like “Base is uracil” in dependent claim 9).
  • W: two-atom options (S vs O), which can be a major contributor to scaffold variability while preserving core pharmacophore.
  • R4/R5/R6/R7: each constrained to relatively small functional sets:
    • hydroxyl/alkoxyl/amino or alkylamino classes for some
    • halogen or alkyl for R6
  • X/Y: the most expansive variables.
    • Each is independently selectable, so the claim space grows roughly multiplicatively across the X × Y option sets.
    • Inclusion of N-linked and O-linked amino-acid residues means X and/or Y can switch between simple heteroatom substituents and bulky peptide-like substituent motifs.
  • S_C: the breadth is concentrated in the allowed side-chain identities and “derivative” forms of amino acid side chains (including thiols, protected amines, carboxyl variants, and various substituted alkyl/arylalkyl/heterocycloalkyl classes).

Infringement implications

  • Literal infringement can be achievable by products that match a particular instantiation of Formula 3001 and its substituent definitions.
  • If competitors design around by replacing the amino-acid linkage type (N-linked vs O-linked) or by removing the amino-acid residue functionality entirely, they can fall outside the literal scope.
  • If competitors use close functional substitutes within the listed enumerations (e.g., alkoxyl vs hydroxyl, or amino acid side chains within S_C list), they remain exposed to literal coverage.

What are the dependent claims that narrow Formula 3001 in US 10,005,779?

The claims provided include multiple dependent layers:

Sublayer: X/Y linkage and residue specificity

  • Claim 2: X is --NH-G(S_C)-C(O)-Q^1, and S_C is a side chain of a naturally occurring amino acid.
  • Claim 3: X is --OR^1, and R^1 is “unsubstituted -alkyl-S-C(O)-alkyl.”
  • Claim 4: Y is broadened to the same class list, while Z is restricted to hydrogen/hydroxyl/halo.

Sublayer: heteroatom at W

  • Claim 5: W is O (limiting the S/O choice to oxygen).

Sublayer: “Formula II–IV” and alternate structured embodiments

  • Claim 6: compound of claim 1 “according to any of Formulas II–IV,” implying the specification defines additional sub-structures under the umbrella of Formula 3001.

Sublayer: alternative Base-dependent constraints (claim 7–8)

  • Claim 7: Base substituted with a specific Base definition and tighter limits on R4–R7.
  • Claim 8: tight embodiment:
    • Base is a specific drawn structure
    • Y defined to allowed classes
    • R^1 is alkyl/aryl/arylalkyl/cycloalkyl/heterocycloalkyl or “-alkyl-S-C(O)-alkyl”
    • X is --NH-G(S_C)-C(O)-Q^1
    • S_C natural amino-acid side chain
    • G is methylene
    • Q^1 is unsubstituted alkoxyl

Sublayer: explicit “uracil” and limited substituent embodiments

  • Claim 9: Base is uracil.
  • Claim 10: R^A is hydrogen or methyl.
  • Claim 11: Z is hydroxyl.
  • Claim 12: R^B is hydroxyl.

Sublayer: “Formulas 1–4” and drawn embodiment set

  • Claim 13: compound of claim 1 according to Formulas 1–4.

Sublayer: compositions

  • Claims 14–15 and 20–21:
    • claim 14: pharmaceutical composition with excipient
    • claim 15: oral formulation
    • claim 20: composition of claim 8
    • claim 21: oral formulation of claim 20

Sublayer: treatment method and combination therapy

  • Claims 16–19:
    • claim 16: treat HCV infection with compound of claim 1
    • claim 17: add second antiviral agent categories in combination or alternation
    • claim 18: second agent includes specific DAAs/interferons (samatasvir/simeprevir/sofosbuvir/telaprevir/boceprevir and interferon formulations)
    • claim 19: same set but explicit exclusion of combination or alternation with ribavirin
  • Claims 22–23: analogous method claims based on claim 8 compound.

Net effect: The dependent claims reduce breadth but still sit within an expansive genus because they still retain variable substitution lists and amino-acid residue options.


Which hepatitis C “MOA” does the method claim cover, and how do combination claims change risk?

Method-of-use claim (claim 16 and 22):

  • Treating a human host infected with HCV by administering an effective amount of the compound.

Combination framework (claim 17 and 23):

  • The method expands to combination or alternation with a long list of antiviral classes:
    • interferons
    • nucleotide analogues
    • polymerase inhibitors
    • NS3 protease inhibitors
    • NS5A inhibitors
    • entry inhibitors
    • non-nucleoside polymerase inhibitors
    • cyclosporine immune inhibitors
    • NS4A antagonists
    • NS4B-RNA binding inhibitors
    • locked nucleic acid mRNA inhibitors
    • cyclophilin inhibitors

Specific DAA exemplars (claim 18/19 and 18/19 duplicates in dependency):

  • samatasvir
  • simeprevir
  • sofosbuvir
  • telaprevir
  • boceprevir
  • interferon alfacon-1 / interferon alfa-2b
  • pegylated interferon alpha 2a / 2b

Ribavirin carve-out (claim 19):

  • “Further wherein the administration is not in combination or alternation with ribavirin.”

Risk framing

  • If a competitor’s regimen uses the claimed compound together with ribavirin, claim 19 may not apply as written, but claims 16–18 still cover combinations generally.
  • If competitors avoid the claimed compound and instead use only other DAAs, they avoid the method claims.
  • If competitors use the claimed compound plus other DAAs, combination method claims increase litigation exposure even if dosing regimens differ, because the claim covers broad “combination or alternation” administration structures.

What do claims 14–15 and 20–21 protect for oral formulations and excipients?

Composition claims are standard:

  • Claim 14: composition comprising the compound + pharmaceutically acceptable excipient/carrier/diluent.
  • Claim 15: oral formulation.
  • Claim 20–21: same structure but tied to compound of claim 8.

Practical impact

  • These claims are typically easier to infringe if a commercial product contains a claimed compound and is formulated for oral delivery.
  • The excipient/carrier language is broad and usually does not add meaningful design-around leverage unless formulation excludes oral route or avoids containing the exact claimed compound instantiation.

What patents and patent estates commonly overlap with US 10,005,779 for HCV antivirals?

This record cannot be completed from the information provided. A comprehensive landscape requires:

  • the full publication family (continuations/divisionals and PCT counterparts),
  • prosecution history (to see narrowing or argument-based estoppel),
  • the specification’s numbered embodiments that correspond to Formulas (1–4, II–IV, 3001),
  • and cross-referencing to competing HCV nucleoside/non-nucleoside/NS5A/NS3 classes.

Because those elements are absent, only the internal structure-based scope of US 10,005,779 can be analyzed from the claim text you supplied.


What is the likely claim strength based on language breadth alone?

Strength indicators

  • Chemical genus and broad Markush options can create a wide literal-infringement surface.
  • Inclusion of amino-acid residue/derivative moieties suggests a defined structural handle that can be difficult to fully remove without changing compound class or losing target binding.
  • Method-of-use claims cover broad combination classes and name specific major DAAs, which often increases leverage in settlements if the compound enters clinical use.

Vulnerability indicators

  • The scope is anchored to specific “Base” structures and a Formula-defined scaffold. If competitors’ active ingredients sit outside that scaffold or use a different heterobase/w substitution (e.g., W not matching S/O requirements), they may avoid literal coverage.
  • If litigation is driven by dependent-claim embodiments (e.g., Base=uracil, W=O, Z=hydroxyl), competitors can design toward non-covered parameter sets even while remaining chemically related.

How do competitors design around Formula 3001 claims using structural alternatives?

Design-around leverage logically targets the biggest discriminators in your claim text:

  1. Remove the amino-acid residue linkage (X or Y)

    • If the competitor avoids N-linked/O-linked amino-acid residue architectures, it may exit the X/Y defined classes.
  2. Change the linkage type

    • If the competitor uses only O-linked or only N-linked linkages, it can attempt to avoid the specific linkage combinations used in the formulation that matches X/Y choices.
  3. Modify W

    • Switching between O and S is a single-atom edit. If the market product is constrained to one form that does not match the competitor product’s actual W value, it can avoid certain dependent claim subsets (e.g., claim 5 W=O).
  4. Avoid specific Base instantiations

    • Dependent claim 9 “Base is uracil” can be avoided by selecting a different Base.
    • More broadly, if the competitor never uses the allowed Base structures under Formula 3001, it can avoid claim 1 entirely.
  5. Avoid targeted combination with ribavirin carve-out

    • If claim 19 is asserted, avoiding regimens that exclude ribavirin alternation/combination could matter. But claim 17 and claim 18 still cover broad combinations.

When does exclusivity end, and what launch risk exists for generics/biosimilars?

A complete exclusivity and generic risk assessment requires:

  • the drug’s approved name and NDA/BLA,
  • Orange Book listings (for active ingredient and dosage form),
  • FDA exclusivity (new chemical entity/new therapeutic biological product, orphan, pediatric, etc.),
  • patent expiration dates and listed patent numbers (including method patents listed for the NDA).

Those data are not supplied here. As a result, no accurate end-of-exclusivity timeline or launch-risk quantification can be produced from the claim text alone.


Key takeaways

  • US 10,005,779 is an HCV antiviral chemical-genus patent with strong breadth from extensive substituent enumerations for Formula 3001, plus composition and method-of-use coverage including oral formulations and combination/alternation with multiple DAA/interferon classes.
  • The highest design-around leverage is structural: changing the Base, the W heteroatom, and especially avoiding the defined X/Y amino-acid residue linkage architecture.
  • Combination method claims increase infringement pathways for clinicians and commercial teams because they cover coadministration/alternation broadly and name major DAAs.
  • A full “comprehensive and critical analysis” of the US patent claim set against the external patent landscape cannot be completed without the patent’s bibliographic record, family members, and Orange Book/FDA regulatory linkages.

FAQs

  1. Does US 10,005,779 cover both N-linked and O-linked amino-acid residue derivatives?
    Yes. Claim 1 defines X and Y as independently hydrogen, small heteroatom substituents, or N-linked and O-linked amino-acid residue/derivative constructs.

  2. Is the patent limited to oral dosing forms?
    No. It includes oral formulation composition claims (dependent), but the core method claims cover treatment by administering an effective amount, not limited by route in the provided claim text.

  3. Can a regimen using ribavirin avoid coverage under US 10,005,779?
    The specific dependency in claim 19 states “not in combination or alternation with ribavirin,” but other combination method claims remain broader.

  4. What parameter is most likely to create a clean structural carve-out: W, Base, or X/Y?
    X/Y are the largest scope drivers because they include both simple substituents and amino-acid residue linkages, with extensive side-chain options.

  5. Is the patent restricted to a single HCV drug partner in combination therapy?
    No. The claims list multiple antiviral classes and named DAAs/interferons as the second antiviral agent.


References

  1. US Patent 10,005,779 (claim text provided by user).

More… ↓

⤷  Start Trial

Details for Patent 10,005,779

Applicant Tradename Biologic Ingredient Dosage Form BLA Approval Date Patent No. Expiredate
Merck Sharp & Dohme Llc INTRON A interferon alfa-2b For Injection 103132 June 04, 1986 ⤷  Start Trial 2034-06-04
Merck Sharp & Dohme Llc INTRON A interferon alfa-2b For Injection 103132 ⤷  Start Trial 2034-06-04
Merck Sharp & Dohme Llc INTRON A interferon alfa-2b Injection 103132 ⤷  Start Trial 2034-06-04
Kadmon Pharmaceuticals Llc INFERGEN interferon alfacon-1 Injection 103663 October 06, 1997 ⤷  Start Trial 2034-06-04
>Applicant >Tradename >Biologic Ingredient >Dosage Form >BLA >Approval Date >Patent No. >Expiredate

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.