So much misinformation and confusion about the circulating #SARSCoV2 variants in India. Leaving aside that the names are scientifically inaccurate, #B1618 ("Bengal variant") is NOT the #tripleMutant. I will try to summarize the basics in this thread.

(1/n)
B.1.617: characterized by more than 15 mutations, it got dubbed the "double mutant" because of two spike mutations, L452R and E484Q, which were mutations of concern because of their immune escape properties, and possible high infectivity.


(2/n)
What's more, there are several sequences of B.1.617 which don't have the E484Q mutation, now sampled in India and elsewhere, which means it's not even the OG "double mutant" anymore.

(3/n)
Triple Mutant: Again, WRONG name, because it has many more defining mutations. Dubbed "triple" because in addition to the two mutations, it also has V382L in its Spike. This is a sub-lineage of B.1.617, found mainly in MH samples and also a bit in other states.

(4/n)
The extra mutation, V382L, is just a mutation of "interest" at this point because it's in the RBD of Spike, and was listed as a low frequency in the US. So far, its frequency seems to remain low and constant.

biorxiv.org/content/10.110…

(5/n)
Whether V382L causes more spread, let alone "more lethal" as touted by the news, remains to be studied. But given its behavior elsewhere so far, it probably less likely to be "destructive".

(6/n)
And lastly B.1.618: First sampled in WB late Oct 2020, it has nothing to do with B.1.617, except for a couple of shared variants that all SARS-CoV-2 strains have at this point such as D614G.



(7/n)
The main concern with #B1618 is that it's found in growing proportions in WB, and has the Spike del145-146 as well as E484K, both of which are known immune escape mutations. E484K in particular was seen before in both B.1.351 and P.1 lineages.


(8/n)
In short, the names of "double" and "triple" mutants are wrong and misleading. And they have no connection to the lineage seen in WB. I have seen even respected news sources getting this wrong. We have enough problems currently, without adding misinformation to the list.

(9/n)
I urge journalists to do a bit more research before writing fear-mongering articles. If something is not clear, please do get in touch with the scientists whose tweets you are quoting. I'm positive they will be happy to explain things in more detail.

Thank you 🙏

(10/10)

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Divya Tej Sowpati

Divya Tej Sowpati Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @TejSowpati

19 Sep 20
Our updated analysis on #SARSCoV2 clades in India, now peer-reviewed and published in OFID by @OxUniPress. In collaboration with @vinodscaria @IGIBSocial. Congratulations to the entire team.
doi.org/10.1093/ofid/o…
#Genomics #IndiaFightsCOVID19
I’ve never done one of these before, but I’m gonna make a thread of tweets explaining the key findings, and more importantly what our paper doesn’t show. 1/n
First and foremost, there is no conclusive evidence at present that any clade of SARS-CoV-2 is associated with increased mortality or severity of the disease. 2/n
Read 11 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!