"Hepata-" Anything: The Name FDA Flagged in 2000

which product names does the preamble name as disease claims?

The 2000 preamble names three product names outright as disease claims: Hepatacure, Carpaltum and Raynaudin. Each one is built from a body part or a condition — liver, wrist, Raynaud's phenomenon — dressed up as a brand. FDA treats the name itself as evidence of intended use, independent of anything printed on the label around it. That's the detail most liver-supplement brands skip: naming risk exists before a single sentence of body copy gets written.

A product name is evidence FDA cites first, not last.

Under 21 CFR 101.93(g)(2), the product name sits alongside formulation, citations, disease terminology and imagery as one of ten enumerated ways a statement becomes a disease claim. The regulation doesn't treat naming as a lesser risk than copy. It lists the name in the same breath as the words printed on the bottle.

why are "hepatacare" and "hepatahealth" presumptively contaminated?

Because FDA reads the syllable "Hepata-" as a likely reference to hepatitis unless the labeling proves otherwise. The preamble states it plainly: "'Hepata' could be read as a reference to hepatitis, unless the labeling made clear that the product was intended for general liver health," per FDA's 2000 final rule. If your working name starts with that root, treat it as presumptively contaminated until proven otherwise.

The presumption isn't limited to the two names FDA listed. Any "Hepat-" construction invites the same reading, because the agency's logic turns on the syllable itself, not on the specific word FDA happened to cite in 2000. A brand built on "Hepato-" or "Hepa-" faces the identical question a reviewer would ask about HepataCare.

what labeling context does fda say rebuts the presumption?

FDA's own cure is narrow and specific: state that the product targets general liver health, not the treatment or prevention of hepatitis, and place that context on the same labeling the name appears on. That's a different mechanism from the standard 21 CFR 101.93(c) boilerplate, the sentence beginning "This statement has not been evaluated by the Food and Drug Administration." The boilerplate doesn't rescue a claim that has already crossed into disease territory — we checked, and 101.93(f) says so directly. The naming fix works differently: it shapes what the name means before the disease-claim test even applies, rather than excusing a claim after the fact. That's worth stating clearly, because most brands assume the only fix for a risky name is renaming, and the preamble doesn't actually require that.

is the same reasoning still being applied twenty-five years later?

Yes. FDA cited a nearly identical liver-branding problem in a warning letter dated November 17, 2025, roughly a quarter-century after the preamble. In the Swadesii letter, FDA quoted label copy reading, "Bhargava Hepatina Syrup is helpful in the treatment of liver problems such as jaundice and fatty liver," on a product called Hepatina Syrup, per FDA's warning letter to Swift Digital Group LLC dba Swadesii. The letter built its case from the descriptive text, not the name alone.

Liver-niche copy runs into a parallel disease-claim trap on the hangover-recovery angle, one we've tracked in The Hangover Angle Is a Disease Claim to FDA. The same 2000 preamble treats that framing as an express disease claim, not a soft structure/function angle.

how does a name violation differ from a copy violation in practice?

A name violation and a copy violation get flagged by the same regulation but they get repaired by very different means, and that difference changes the cost of fixing them. Renaming a SKU means new labels, sometimes new molds, and a fresh 30-day notification filed with FDA's Office of Dietary Supplement Programs. Rewriting a paragraph means editing a page and republishing it, often within a day. The table below lays out where each failure mode originates and what fixing it actually requires.

FDA's letter to New Sun quoted the copy directly: "Milk thistle is used as a natural aid for liver problems. These liver problems may include cirrhosis, jaundice, hepatitis and gallbladder disorders," per FDA's warning letter to New Sun Inc.. The product name, Advanced Liver Plus, was never in question.

The paragraph did all the damage.

does a domain, ad headline or landing-page h1 carry the same risk?

Yes. FDA's naming trigger reads "product name" broadly enough to include the URL and the headline, not just the SKU printed on the physical label. FDA's warning letters routinely treat a company's domain, its blog posts and its Amazon listing headline as labeling for intended-use purposes, exactly as they treat the panel glued to the bottle, and the naming trigger under 101.93(g)(2)(iv) reaches the product name wherever a buyer encounters it — a URL slug, an ad headline, or a landing-page H1 set in bigger type than anything else on the page. A domain like hepatahealthcure.com carries the same "Hepata-" ambiguity the preamble flagged for a bottle label, and a page that never once uses the word "hepatitis" in body copy can still fail the test if its H1 does the naming work instead. This is the same structural gap that runs through detox claims, where FDA never defined the term and left every claim to be judged from surrounding context alone — there's no safe-harbor sentence anywhere to point to, only the words and where they sit on the page.

We could not find a warning letter in this niche built on a domain name alone, independent of any body copy naming the condition. What would settle the question is a published FDA letter citing a URL or ad headline as the sole naming trigger, with no accompanying text cited alongside it.

what naming checklist should run before a sku is locked?

Run five checks before you lock a SKU name, not after the label printer already has the file.

• Search the working name for "Hepat-," "hepato-," or any other disease-adjacent root before it reaches a mockup.
• If the root survives, draft FDA's rebutting sentence — general liver health, not treatment or prevention of hepatitis — and place it on the same panel as the name.
• Check the domain and every ad headline for the same root, since the naming trigger travels with the brand mark, not just the bottle.
• File the 30-day structure/function notification under the brand owner's name, a duty that belongs to the brand rather than the co-packer, as we outline in [The Name on the Label: FDA Duties That Belong to the Brand, Not the Co-Packer](/niches/the-name-on-the-label-fda-duties-that-belong-to-the-brand-not-the-co-p).
• Route the finalized name and rebuttal language past whoever signs the substantiation file, since FTC's evidence bar runs on a separate track from FDA's naming rule.

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For external context, readers should compare advertising and research decisions against authoritative primary references such as FTC health claims guidance, Meta advertising standards, and Meta Ad Library. Daily Intel adds the proprietary direct-response layer: blackhat, greyhat, and whitehat campaign pattern comparison across VSL-heavy niches and 14+ language markets.

For deeper evaluation, continue through Nutra niche intelligence directory, Lung and Respiratory Offers: Small Market, Steep Claim Ceiling, Inflammation Offers: The Umbrella Angle Everyone Borrows, Bone Density Offers: Market, Buyer, and the Osteoporosis Line, Sinus and Allergy Offers: Seasonal Demand, Drug-Category Competition, and GLP-1 affiliate marketing intelligence. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.