Leqvio (Inclisiran) and Rivaroxaban Interaction: What Clinicians and Patients Should Know

What each drug is, and why that matters here

Leqvio (inclisiran) is a synthetic double-stranded siRNA conjugated to triantennary N-acetylgalactosamine (GalNAc), which targets it to hepatocyte asialoglycoprotein receptors [1]. Inside the liver cell it loads into the RNA-induced silencing complex (RISC) and cleaves PCSK9 messenger RNA, reducing PCSK9 protein synthesis. With less PCSK9 available, LDL receptors persist longer on the hepatocyte surface and clear more LDL particles from circulation. It is dosed as a 284 mg subcutaneous injection at month 0, month 3, and every 6 months thereafter, administered by a healthcare professional [1].

Xarelto (rivaroxaban) is a small-molecule direct Factor Xa inhibitor. It is FDA-approved for stroke and systemic embolism prevention in nonvalvular atrial fibrillation, for treatment and secondary prevention of venous thromboembolism, and for reducing cardiovascular events in patients with chronic coronary or peripheral artery disease [3]. Unlike inclisiran, rivaroxaban undergoes substantial hepatic metabolism and transporter-mediated handling, which is the source of its known interaction risks.

The core answer, stated plainly: inclisiran and rivaroxaban have no documented pharmacokinetic interaction because inclisiran is degraded by nucleases rather than metabolized by CYP450 enzymes or transported by P-glycoprotein, while rivaroxaban's clinically significant interactions arise specifically from CYP3A4, CYP2J2, and P-gp/BCRP pathways that inclisiran does not touch [1][3]. This is a mechanism-based inference drawn from each drug's own labeled pharmacology, not a finding from a study that directly co-administered the two agents in the same patients. Clinicians should treat this as reassuring but not as proof of studied safety.

How inclisiran avoids the pathways that matter for rivaroxaban

For a pharmacokinetic interaction to occur, two drugs generally need to share a metabolic enzyme, a transporter, or a binding target. The Leqvio label describes inclisiran as not being a substrate, inhibitor, or inducer of the major CYP isoforms (1A2, 2B6, 2C8, 2C9, 2C19, 2D6, 3A4), and not a substrate of P-gp, BCRP, OATP1B1/1B3, or organic cation transporters [1]. Instead, plasma and tissue nucleases break inclisiran down into inactive nucleotide fragments cleared by the kidneys.

Rivaroxaban's profile is different. Roughly two-thirds of a rivaroxaban dose is metabolized hepatically, with CYP3A4 responsible for an estimated 18% of total elimination and CYP2J2 for about 14%; the remainder involves CYP-independent oxidative pathways [3]. Rivaroxaban is also a substrate of P-gp and BCRP efflux transporters [3]. The Xarelto label advises against combining rivaroxaban with drugs that are both strong CYP3A4 inhibitors and P-gp inhibitors (such as ketoconazole, itraconazole, or ritonavir) or with combined strong CYP3A4/P-gp inducers (such as rifampin, carbamazepine, or phenytoin) [3]. A pharmacokinetic study found that ketoconazole increased rivaroxaban's AUC by roughly 150% and rifampin decreased it by roughly half [4]; these are large enough shifts to matter clinically for a narrow-therapeutic-window anticoagulant.

Because inclisiran does not inhibit, induce, or compete for any of these enzymes or transporters, it cannot raise or lower rivaroxaban exposure through the mechanisms that make ketoconazole or rifampin risky. The reverse also holds: rivaroxaban's CYP3A4 substrate status has no bearing on inclisiran, since inclisiran's clearance never passes through CYP-mediated metabolism.

Protein binding is a secondary consideration. Inclisiran is approximately 87% protein-bound and rivaroxaban is 92-95% protein-bound, mostly to albumin [1][3]. Neither label flags protein-binding displacement as a clinical concern for these agents, and displacement interactions at therapeutic concentrations are generally not expected to be meaningful for either drug.

Evidence-status assessment: inclisiran plus rivaroxaban

A clinician or pharmacist reviewing this combination should confirm the current FDA label revision for both drugs (labels linked above were current as of 2021 and may have been updated since), check the patient's renal function given rivaroxaban's renal dosing thresholds, and review the full medication list for other CYP3A4 or P-gp modulators, since those, not inclisiran, are the actual interaction risk for a rivaroxaban regimen.

What the ORION trials show about concomitant medication use

The ORION program enrolled patients with atherosclerotic cardiovascular disease or ASCVD risk equivalents, populations in which anticoagulant use is common. In ORION-10 (N=1,561), inclisiran 284 mg produced a placebo-adjusted LDL-C reduction of 52.3% at day 510 (P<0.001) [2]. In ORION-11 (N=1,617), the time-averaged placebo-adjusted LDL-C reduction from day 90 to day 540 was 49.2% (P<0.001) [5]. Patients in both trials continued their existing cardiovascular medications, which for some participants would have included oral anticoagulants, though the trials were not designed to isolate an inclisiran-anticoagulant interaction signal.

A pooled patient-level safety analysis across the ORION program (N=3,655 inclisiran-treated patients) reported injection-site reactions as the most common adverse event, occurring more often with inclisiran than placebo, and did not identify a signal of excess bleeding or thromboembolic events attributable to inclisiran [6]. The exact percentages cited in earlier drafts of this material should be re-confirmed against the full published analysis before being repeated as precise figures in patient-facing material.

A separate pre-specified analysis from the ORION-1 trial examined platelets, immune cells, and immunological biomarkers and did not report adverse platelet or immune effects attributable to inclisiran [7]. This is relevant background for bleeding-risk reasoning, though it is not a direct test of the rivaroxaban combination.

An inclisiran cardiovascular outcomes trial (ORION-4) was designed with a large enrollment to evaluate major adverse cardiovascular events, but this article does not have a verified source confirming its enrollment size or completed results, so no specific figures are stated here. Readers seeking the current status of ORION-4 should check ClinicalTrials.gov or the sponsor's most recent disclosures.

Pharmacodynamic reasoning: why lipid-lowering and anticoagulation don't overlap

Pharmacokinetic neutrality is not the same as clinical simplicity. Patients on both inclisiran and rivaroxaban are, by definition, high cardiovascular risk patients with long medication lists, and that context matters more than the inclisiran-rivaroxaban pair itself.

Inclisiran lowers LDL-C through PCSK9 suppression and has no known direct effect on coagulation factors or platelet function. Rivaroxaban inhibits Factor Xa and carries a well-characterized bleeding risk. These two effects do not overlap: inclisiran will not potentiate rivaroxaban's anticoagulant effect, and rivaroxaban will not blunt inclisiran's lipid-lowering activity, based on the mechanisms described in each label.

The real bleeding-risk conversation in these patients usually concerns antithrombotic combinations, not inclisiran. The COMPASS trial (N=27,395) found that rivaroxaban 2.5 mg twice daily plus aspirin reduced the composite of cardiovascular death, stroke, or myocardial infarction by 24% compared with aspirin alone, while increasing major bleeding (3.1% vs 1.9%, P<0.001) [10]. The 2023 AHA/ACC chronic coronary disease guideline recommends individualizing antithrombotic therapy and limiting the duration of combined anticoagulant-antiplatelet regimens where feasible, because of the added bleeding risk from that combination [9]. That guidance is about rivaroxaban plus antiplatelet therapy, not about inclisiran, but it is the relevant bleeding-risk conversation for these patients.

Monitoring: what actually needs to be checked

No additional laboratory monitoring is required specifically because a patient takes both drugs together. Standard monitoring for each drug individually remains the right approach.

• Lipid panel: the Leqvio label recommends checking LDL-C 4 to 8 weeks after the first dose and periodically thereafter, which aligns naturally with the twice-yearly dosing schedule [1].
• Renal function: the Xarelto label specifies dose adjustments for atrial fibrillation patients with creatinine clearance 15-50 mL/min (15 mg daily instead of 20 mg) and avoidance below 15 mL/min, so renal function should be checked at baseline and at least annually, more often if declining [3].
• Liver function: reasonable at baseline for both drugs. Trial data have not shown a clear hepatotoxicity signal for inclisiran; rivaroxaban's label notes rare post-marketing reports of hepatic injury and advises prompt evaluation if signs of liver disease appear [3].
• Bleeding assessment: a clinical conversation at each visit, focused on the rivaroxaban regimen (and any concurrent antiplatelet therapy) rather than on inclisiran.

When this combination warrants a conversation with a prescriber

Patients should tell their prescriber about every medication, including inclisiran, before starting or changing an anticoagulant. That is not because inclisiran interacts with rivaroxaban, but because prescribers need the complete list to catch the interactions that do matter for rivaroxaban itself.

Situations that genuinely warrant discussion:

• Starting a new strong CYP3A4 inhibitor or inducer (affects rivaroxaban, not inclisiran)
• Adding antiplatelet therapy to rivaroxaban (raises bleeding risk independent of inclisiran)
• Declining renal function below CrCl 50 mL/min (may require a rivaroxaban dose change)
• Planning surgery or an invasive procedure (rivaroxaban may need temporary interruption; inclisiran does not)

Inclisiran's twice-yearly, clinician-administered injection is a natural checkpoint for reviewing the full medication list and renal function, even though it is not driven by an inclisiran-rivaroxaban interaction concern.

Evidence boundary

What is established: inclisiran's clearance pathway (nuclease degradation, not CYP or P-gp) and rivaroxaban's clearance pathway (partial CYP3A4/CYP2J2 metabolism, P-gp/BCRP transport) are described independently in each drug's FDA label, and these pathways do not overlap.

What is plausible but not directly tested: that this non-overlap means no clinically meaningful interaction occurs when the two drugs are taken together in real patients. No dedicated inclisiran-rivaroxaban co-administration trial was identified for this article.

What is not established: long-term safety or effectiveness outcomes specific to patients taking both drugs concurrently, and precise adverse-event rates attributable to that specific combination. General ORION safety data describe inclisiran's overall adverse-event profile, not a rivaroxaban-specific subgroup.

This article does not provide individualized dosing or diagnostic advice. Patients with questions about their specific regimen, renal function, or bleeding risk should discuss them directly with the prescriber managing their anticoagulation and lipid therapy. Anyone experiencing unusual bleeding, bruising, or signs of an allergic reaction after a Leqvio injection should seek prompt medical evaluation.