TB-500 in the HHS Draft: Fragment Identity, Routes, and Evidence

TB-500 is one of six names in the HHS draft’s Appendix A. The Federal Register notice calls the associated enforcement-discretion document a draft and says it is not binding on HHS or the public. It is scheduled for publication October 30, 2026, with a comment period extending two weeks after publication. Readers should verify subsequent developments before interpreting it as an implemented access policy.

This is a proposal concerning certain 503A compounding circumstances. It is not an FDA drug approval for injury recovery, athletic performance, or another indication. The approval-versus-discretion explainer describes why these regulatory categories answer different questions.

Not for purposes of interpreting this draft. Appendix B identifies TB-500 acetate with the sequence Ac-Leu-Lys-Lys-Thr-Glu-Thr-Gln-OH, an acetylated seven-amino-acid fragment. Full-length thymosin beta-4 is a different molecule. A product label or research article using one name loosely should not erase that distinction.

The identity statement in Appendix B is particularly important because HHS discusses a controlled human safety record for the parent protein when explaining its reasoning. That is supporting context in its policy assessment; it does not mean the same studies tested this exact fragment. Before relying on a result, establish the actual molecule studied, its formulation, route, and population.

The specified form is TB-500 acetate, in subcutaneous or intramuscular injectable dosage forms. Intravenous, oral, and topical TB-500 are not established by that route statement. Nor does it cover every salt or every product marketed under the same short name. The identity requirements are part of the proposed safeguards, not optional labeling details.

The draft also requires a single API. A combined BPC-157/TB-500 product does not become covered merely because each ingredient appears separately in Appendix A. Compare the separate BPC-157 conditions, which name a different set of routes, without assuming those routes transfer to TB-500.

HHS describes lot-specific certificates from FDA-registered manufacturers supplying identification, assay, impurity, endotoxin, microbial, and residual-solvent results that it says were previously missing. It also describes newly quantified historical compounding use. These developments address whether the substance is characterized and how it has been used; they are not equivalent to a large trial showing a treatment benefit.

The draft characterizes earlier safety concerns as inferential, mentions evidence concerning the parent protein, and notes rapid truncation of the fragment in human serum. A molecular breakdown observation does not itself establish an effective clinical regimen or eliminate the possibility of harm. The document supplies a policy rationale rather than an approved prescribing label.

In its July 2026 advisory briefing, FDA reported finding no medical-literature information in which TB-500 was administered to patients for any disease or condition, including wound healing. That assessment concerned the fragment and predates the HHS draft’s later rationale. The gap should remain visible when advertisements cite research on full-length thymosin beta-4 or extrapolate from laboratory findings. FDA TB-500 briefing

The FDA’s April 22, 2026 safety page specifically names thymosin beta-4 fragment, LKKTETQ, also known as TB-500. It describes potential immunogenicity and peptide-related impurities and says FDA had not identified human exposure data for drug products containing the fragment. The date matters: that is a historical FDA account, while the later HHS draft discusses additional submissions and a different policy assessment.

Neither source supports describing TB-500 as conclusively safe or proven to speed healing. Evidence for a related molecule, documented prescribing history, and laboratory purity can each be relevant without answering the same clinical question. Patients need the uncertainty explained in terms of their own proposed use.

Ask the pharmacy to identify the exact API, original manufacturer, intended route, and current basis for compounding. Under the draft, the original manufacturer would need FDA registration and CGMP compliance, and the COA would need appropriate identity and quality testing. Serious adverse events and quality issues would be reported, with instructions available to the patient.

A clinician should separately explain the diagnosis, reasonable alternatives, what evidence supports using this exact fragment, and how outcomes and adverse effects would be followed. The draft does not establish a dose or guarantee a prescription. A supplier’s “research” label and a laboratory certificate are not substitutes for patient-specific clinical care or verification of the policy’s current status.