... | File- Blood.fresh.supply.v1.9.10.zip

Someone had leaked this. Someone on the inside.

“Jim, I need you to look at something. And I need you to promise you won’t ask where it came from until after you’ve looked.” Kettering was silent for three full minutes after Maya walked him through the database. Then:

Predicted rejection rate without protocol: 68% (for mismatched donors). Predicted rejection rate with protocol (v1.9.10): 0.4%. File- Blood.Fresh.Supply.v1.9.10.zip ...

Dr. Maya Ramesh, senior data analyst for the Global Pathogen Surveillance Initiative (GPSI), first noticed it during a routine sweep of new genomic uploads. The naming convention was odd. Most researchers used plain identifiers: H7N9_Shanghai_2024.fasta , Ebola_reston_2023.fasta , SARS_CoV_2_variant_BQ.1.18 . This one had the cadence of a software version—v1.9.10—and the word “Blood” in lowercase, then a period, then “Fresh.Supply,” then another period. As if the file itself were a specimen label, but for something that had been updated nine times.

Size: 47.2 MB Source: Unknown Uploaded: 3:14 AM GMT Someone had leaked this

Maya hesitated. Then she downloaded a sandboxed copy. The first thing she saw after unzipping was the readme. No greeting, no lab letterhead, just a single line in monospaced font: "This is not a weapon. It is a mirror. Run main.db against any population sample with known HLA typing." HLA typing. Human leukocyte antigens—the molecular barcodes that tell the immune system friend from foe. Maya’s heart ticked up a beat.

She should have flagged it for the encryption alone. Open science was the rule in pathogen genomics. Unbreakable encryption meant someone had something to hide. But the system didn’t auto-flag because the header wasn’t malicious—it was just… strange. And I need you to promise you won’t

She felt suddenly, irrationally cold. Then she realized—she had donated blood at a drive last month. Standard Red Cross. They always stored samples for quality control.