Steve Massey Profile picture
Apr 16 15 tweets 4 min read Read on X
We received an (indirect) response from UNC regarding our preprint outlining evidence for a potential lab leak of SARS2 at UNC

UNC asked GISAID to tell us to remove our preprint

We did this, but have now put up an updated version 🧵
zenodo.org/records/151721…
2/ @quay_dr uploaded our original preprint on March 26

We identified 7 'frozen' SARS2 sequences from UNC, that were basal to other sequences generated at the same time. These could represent early SARS2 strains that had escaped from a research facility

3/ Before uploading the preprint, we sent an email to Dirk Dittmer and Melissa Miller of the Clinical Molecular Microbiology Laboratory, UNC Hospital, regarding the 7 anomalous sequences we had detected from their sequencing facility

However, they did not respond Image
4/ We also sent an email to Dr Derek Kemp, the UNC Associate Vice Chancellor for Campus Safety and Risk Management, alerting him to our preprint and asking for clarification

However, we received no response Image
5/ UNC have not contacted my co-author @quay_dr or myself directly

Rather, both UNC and the CDC (!?) contacted GISAID, who then phoned @quay_dr to take down our preprint as it contained a fasta file of the 7 sequences in the preprint supplementary material
6/ The reason we included the fasta sequences was for reproducibility and transparency

However, GISAID objected that this violated their user agreement and requested that we use a hyperlink to direct investigators to the fasta data, which we were happy to do
7/ This is strange behavior from UNC, and the CDC

Why not address the substance of our preprint, that proposes that the 7 sequences indicate a potential lab leak, rather than engaging in vexatious quibbles ?
8/ The role of the CDC is unclear in this. They are supposed to be an independent agency, why are they lobbying to have UNC-generated sequence data removed from a preprint authored by decentralized investigators ?
9/ One would expect that if an institution is alerted to information that indicates a potential lab leak from one of their facilities, it should address those concerns

This has not happened, rather UNC engaged in evasive tactics, indicating a flaw in biosafety procedures
10/ If this is the response from institutions engaged in dangerous pathogen research to inconvenient sequence data, how can we be assured that in future such sequences are not simply discarded by the sequencing facility, rather than making them public ?
11/ There is currently no proposal to address this key problem in genomic surveillance, that of conflict of interest between sequencing centers and the public

One solution would be to use blockchain to ensure the chain of custody is not violated and information not censored
12/ If sequences can be judged to be 'noisy' or 'artefactual', and removed as a consequence, we need to be sure that this is not used as an excuse to censor bona fide 'frozen' genome sequences, which are one of the red flags indicating a potential leak

mdpi.com/2076-2607/12/1…
13/ The other red flag is the institutional response to public concerns of a potential pathogen leak

In the example reported here, the response of UNC is more consistent with a leak
14/ The nature of anomalous virus sequences can often only be clarified with the cooperation of the originating institution. If that cooperation is not forthcoming then a question mark remains

Any indication of a potential leak should trigger an automatic investigation
@threadreaderapp unroll

• • •

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

Keep Current with Steve Massey

Steve Massey 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 @stevenemassey

Mar 25
Steve Quay @quay_dr and myself have published evidence for a potential lab leak of SARS2 at the University of North Carolina (UNC)

7 genome sequences collected by UNC in 2020-21 are basal (ie 'frozen') indicating a potential lab origin 🧵
zenodo.org/records/150833…
2/ The 7 sequences were collected from Jun 2020 to Jan 2021 and submitted by Dr Dirk Dittmer of the Clinical Molecular Microbiology Laboratory, UNC Hospital

Puzzlingly, they show strong similarities to the SARS2 reference sequence Hu-1, sampled in Dec 2019 Image
3/ On the dates the 7 sequences were collected, they should have accumulated more SNVs than they actually possess, according to the SARS2 molecular clock Image
Read 15 tweets
Mar 15
I've published a paper on the emerging phenomenon of 'frozen' virus genome sequences, and how they can indicate lab leaks

"Frozen' virus genome sequences are generated from recent outbreaks, but show surprising similarity to historic strains 🧵
mdpi.com/2076-2607/12/1…
2/ The classic example is 1977 'Russian' H1N1 Flu, which re-emerged after having gone extinct in the 50s. Genomic sequences were identical to strains from the 50s, indicating it had been stored for > 20 years before release
nature.com/articles/27433…
3/ An alternative scenario of viral host persistence / latency seems unlikely

A clue to its non-natural origin was that only younger people got sick, while older people were immune. This is because the latter had been exposed to H1N1 in the 50s and before
pmc.ncbi.nlm.nih.gov/articles/PMC23…
Read 19 tweets
Mar 12
It has been reported German Intel has assessed that COVID19 originated via a lab leak

Swiss paper NZZ reports that our discovery of a MERS-related infectious clone with a chimeric spike from Wuhan sequencing datasets was considered by German Intel 🧵 Image
2/ The study by @humblesci @Daoyu15 @BiophysicsFL @ydeigin @quay_dr and myself was published last year and demonstrated unreported GOF experimentation on novel MERS-related coronaviruses in Wuhan prior to the pandemic
fortunejournals.com/articles/disco…
3/ Concerningly, we found evidence that a MERS spike (with FCS) was inserted into a HKU4r-CoV backbone, likely enhancing transmissibility in human cells, as the RBD is expected to have a high binding affinity for the hDPP4 receptor

Here is a thread on the preprint version of the paper:
Read 7 tweets
Feb 26
Pekar et al have published a paper claiming that 2 SARS2 A/B intermediates from Feb 2020 are derived rather than ancestral

The existence of ancestral intermediates would falsify Pekar et al's earlier claim of 2 independent spillovers of lineages A and B at the Huanan Market 🧵 Image
2/ Hence Pekar et al undergo extraordinary convolutions in order to try and claim the 2 A/B intermediates, identified by Lv et al 2024, are late arrivals rather than the original intermediates that led to the evolution of lineage B from lineage A

academic.oup.com/ve/article/10/…
3/ To sum, they once again (ab)use modeling to support intuitively unlikely scenarios

They claim it is more likely that the 2 Lv et al intermediates arose from either Hu-1 (lin B), or its closest lin A relative (C8782T,T28144C) AFTER the 2 lineages had originally split
Read 9 tweets
Nov 2, 2024
'Conincidentally' we showed pUC57 was also used to clone a genome fragment from an unpublished pangolin-related SARS2r-CoV from China 🧵

h/t @humblesci @Daoyu15 @ydeigin @quay_dr

mdpi.com/2673-8007/2/4/…

x.com/Engineer2The/s…
2/ This striking conincidence indicates that the novel pangolin-related coronavirus we identified from contaminated datasets (GX_ZX45r-CoV) was likely part of an infectious clone (IC), given that one of the reads was ligated to pUC57

From our paper: Image
3/ This can be inferred given that ZLS et al report using pUC57 for cloning genome fragments of HKU5 coronavirus prior to assembly into an IC in their recent Nature paper on engineering coronavirus receptors

h/t @Engineer2The Image
Read 6 tweets
Sep 18, 2024
I have published a paper on my analysis of the RaTG13 dataset

RaTG13 is the closest phylogenomic relative of SARS2

Transcriptome and GO enrichment analysis indicates the likely source of the dataset is a bat mating plug, rather than a fecal swab 🧵

mdpi.com/2036-7481/15/3…
A mating plug provenance resolves the long standing conundrum over the low amounts of bacteria in the RaTG13 sample, noted by @MonaRahalkar and others, which is inconsistent with a fecal swab as reported by the WIV, who collected the sample
I presented the evidence for a mating plug provenance in a previous thread 👇
Read 10 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

Don't want to be a Premium member but still want to support us?

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

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(