The event in SecBot's records
SecBot's biotech catalyst feed records an FDA approval for ATEBRIOZ on November 3, 2026. It also records an orphan drug designation for brelovitug on that date. Both entries are linked to Mirum Pharmaceuticals. The approval entry identifies ATEBRIOZ as an NDA for fibrodysplasia ossificans progressiva, or FOP. The designation entry names brelovitug for chronic hepatitis delta virus, or HDV. These are distinct regulatory developments involving different medicines and different conditions, not two stages of one application.
The dates matter because a catalyst feed is a record of dated regulatory events, not a company valuation or a measurement of business results. The local record identifies approval of ATEBRIOZ, while the brelovitug item describes an orphan drug designation. The latter is not described as an approval. Keeping that distinction clear is essential to reading this update: one entry records an approval, the other records a regulatory designation.
What the entries say
The approval record labels the catalyst type "fda_approval" and gives the drug name as ATEBRIOZ. Its indication field is fibrodysplasia ossificans progressiva. The application type is NDA. The feed assesses the entry as positive sentiment with high confidence. Those descriptors are part of SecBot's stored catalyst data. They do not provide an FDA review document. The record also lacks a label or a description of the evidence supporting the action.
The separate brelovitug record labels its catalyst type "orphan_drug." It identifies chronic hepatitis delta virus as the indication and also classifies the item as positive sentiment with high confidence. Its details field says FDA Orphan Drug Designation for brelovitug in HDV. Unlike the ATEBRIOZ entry, the application type field is "Unknown." The record therefore does not establish that the designation is an approval, nor does it supply a review timetable or a future action date.
Both catalyst rows carry November 3, 2026, as the catalyst date and filing date. Their shared date supports describing them as same-day entries in the local feed. It does not establish that one regulatory action depended on the other. No such connection is stated in either record.
Different drugs, different indications
The indication fields are the clearest way to separate the two records. ATEBRIOZ is tied to FOP, while brelovitug is tied to HDV. The feed names both medicines and their conditions, but it does not describe how either medicine works. Nor does it give patient eligibility or trial results. The size of either potential patient population is also absent. Those details should not be inferred from a catalyst label.
The application details also differ. ATEBRIOZ has an NDA application type in the record. The brelovitug designation has no specified application type. This is another reason not to treat the two entries as equivalent milestones. An approval entry reports an approval; an orphan drug designation reports a designation. Neither the common company name nor the common date erases that difference.
SecBot's biotech coverage and biotech drug reports provide places to follow the category of data represented here. The MIRM stock page provides company-level context. These pages do not alter the meaning of the underlying catalyst rows: the approval and designation remain separate records with separate indications.
What the nearby data does and does not add
The other local records returned in this research run offer some context about the way catalyst data is presented. A CAPR entry lists a PDUFA target action date for Deramiocel on November 22, 2026. It says that date was extended following submission of additional Phase 3 HOPE-3 data. Separate SMMT entries list November 14, 2026, as a PDUFA date for ivonescimab. These are other companies' timelines and are not evidence about Mirum or its two medicines. They do show why catalyst type and date should be read together: an expected action date is different from a recorded approval or designation.
A separate local FDA action query returned records for other products, including an approval entry dated November 4, 2026, for RELEUKO. The query also returned shortage entries dated November 3, 2026. Those items do not provide further detail about ATEBRIOZ or brelovitug. The press release query for MIRM returned no rows in its selected window. That result means no matching local press-release report was returned by that query; it does not establish that no company announcement exists elsewhere.
There was no MIRM-specific price record or earnings snapshot in the data gathered for this post. The catalyst information therefore does not show a share-price response. It also lacks revenue contribution or changes to company guidance. It should be read narrowly as a dated regulatory update, not as a complete company report.
What the catalyst feed cannot establish
The stored catalyst rows are concise summaries. For ATEBRIOZ, the information available here does not state the precise approved labeling or the date of a public announcement beyond the catalyst date. It does not state conditions attached to the approval. No such details should be supplied from these records alone.
The record also does not provide trial endpoints. It lacks efficacy estimates and safety data. The number of patients studied is not stated. No such values should be supplied from these records alone.
For brelovitug, the record does not state a review outcome or a target action date. Orphan drug designation is the event recorded; the row does not describe what regulatory benefits apply, whether an application has been submitted, or when another decision may occur. The feed's positive sentiment label and high confidence are SecBot classifications, not a substitute for those missing details.
The rows also do not establish commercial availability or pricing. They do not quantify demand or uptake. Nor do they state how much either product may contribute to Mirum's financial results. They contain no sales figures or management forecast. The two entries are important to describe accurately, but the absence of those business measures limits the conclusions available from this dataset.
What to watch in the record
The next useful evidence would be a more detailed company or regulatory filing that spells out the approved ATEBRIOZ label. A filing could also clarify the status of brelovitug beyond its designation. For the latter, a later filing may clarify its development and regulatory path, but the November 3 entry itself does not set a date for another decision. For ATEBRIOZ, a detailed source could clarify the approval's scope. No timeline for either development is stated in the entries used here.
SecBot's local data is updated as ingestors add records, so later reporting may add information not present in this snapshot. The specific checkable facts are the ATEBRIOZ approval entry and the brelovitug designation entry. Their indications are distinct. Both entries are dated November 3, 2026. Further company context is available through the MIRM stock page. To follow SecBot's research updates, visit registration.