From “Unknown Male” to “Catastrophic DNA”: How the Idaho4 Narrative Keeps Getting Rewritten
Major media outlets now report that the alleged Idaho4 “killer” left behind “catastrophic DNA” at the King Road crime scene. Fox News even quoted Othram’s CEO, claiming there were “tons” of DNA and alleging the defense “didn’t want to talk about it.”
But the official court filings and police reports paint a very different picture. Here’s the breakdown—with receipts.
What Fox Claimed vs. What the Court Record Shows
CLAIM: The suspect “left behind ‘catastrophic’ evidence” and there was “tons of DNA.”
RECORD: Court documents describe a single-source male STR profile from a swab of the knife sheath (Item Q1.1). No legal filing uses the word “tons” or “catastrophic.” The judge explicitly directed parties to avoid terms like “touch DNA” or “trace DNA.” Order on Touch/Contact DNA
CLAIM: Investigators had an “ample sample from the snap” and quickly identified the suspect.
RECORD: STR profile from Q1.1 was uploaded to CODIS with no match. Only then did investigators pursue IGG (genetic genealogy) via SNP analysis. The FBI named Kohberger as a lead on Dec. 19, 2022. Order on Genetic Suppression
CLAIM: There was DNA “everywhere.”
RECORD: Defense Motion in Limine #6 confirms the only probative DNA was from the knife sheath. Kohberger was excluded from another DNA mixture found on a separate portion (Item Q1.4). Defense Motion
CLAIM: The article conflates STR and SNP profile types.
RECORD: STR was used for forensic comparison and entry into CODIS (with no match). SNP was used for investigative genealogy to generate leads. The evidence in court is based solely on the STR profile. IGG Order
CLAIM: The DNA quantity was significant or abundant.
RECORD: The lab reported 0.168 ng/µL of DNA on Item 1.1—a minuscule trace. The court warned against using loaded language and ordered technical neutrality during trial. Order on Language Use
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager