Submit a comment

HoxBlinc: a key driver of chromatin dynamics in NUP98 fusion–driven leukemia
Jian Xu, Wei Du
Jian Xu, Wei Du
Published April 1, 2025
Citation Information: J Clin Invest. 2025;135(7):e191355. https://doi.org/10.1172/JCI191355.
View: Text | PDF
Commentary Article has an altmetric score of 3

HoxBlinc: a key driver of chromatin dynamics in NUP98 fusion–driven leukemia

Abstract

Nucleoporin 98 (NUP98) fusion oncogenes are known to promote aggressive pediatric leukemia by disrupting chromatin structure and modulating the expression of homeobox (HOX) genes, yet the precise molecular events are unclear. In this issue of the JCI, K. Hamamoto et al. explore the mechanistic underpinnings of NUP98 fusion–driven pediatric leukemia, with a focus on aberrant activation of the Hoxb-associated long, noncoding RNA (lncRNA) HoxBlinc. The authors provide compelling evidence that HoxBlinc plays a central role in the oncogenic transformation associated with NUP98 fusion protein. The study underscores a CTCF-independent role of HoxBlinc in the regulation of topologically associated domains (TADs) and chromatin accessibility, which has not been fully appreciated in previous research on the NUP98 fusion oncogenes. The discovery of HoxBlinc lncRNA as a downstream regulator of NUP98 fusion oncoproteins offers a potential target for therapeutic intervention in pediatric leukemia.

Authors

Jian Xu, Wei Du

×

Guidelines

The Editorial Board will only consider comments that are deemed relevant and of interest to readers. The Journal will not post data that have not been subjected to peer review; or a comment that is essentially a reiteration of another comment.

  • Comments appear on the Journal’s website and are linked from the original article’s web page.
  • Authors are notified by email if their comments are posted.
  • The Journal reserves the right to edit comments for length and clarity.
  • No appeals will be considered.
  • Comments are not indexed in PubMed.

Specific requirements

  • Maximum length, 400 words
  • Entered as plain text or HTML
  • Author’s name and email address, to be posted with the comment
  • Declaration of all potential conflicts of interest (even if these are not ultimately posted); see the Journal’s conflict-of-interest policy
  • Comments may not include figures
This field is required
This field is required
This field is required
This field is required
This field is required
This field is required
Rich Text Editor, eletter_body