In that tweet, I included the following table:
The table outlines the last modification dates on the emails (batched by date) and shows the earliest and latest timestamps, minimum ID, maximum ID, count and a column titled “FAT.”
What the table illustrates is that the first batches of DNC emails published by WikiLeaks have times that indicate the files were likely transferred to a FAT file system (likely transferred via a USB storage device).
Having received several queries concerning this, I wanted to give a more detailed explanation and, as further observations have been made, to report on these and make some clarifications.
FAT File System Indicators
The “FAT” column is in reference to the FAT file system, a file system that, in recent years, is usually used on USB storage devices (some outdated non-USB disk storage devices used this in the past too, but it’s very rare to find such devices still in use).
One of the shortfalls of the FAT file system is that it stores timestamp data at a lower resolution (to the nearest two seconds). However, this is advantageous for the purpose of digital forensics as it means there is a pattern that can be detected and used to determine whether files were likely to have been transferred via a FAT file system.
The batches of DNC emails that appear to have been copied to a FAT file system due to this pattern have an “x” in the “FAT” column (in the table referenced at the beginning of this article).
The First Two Batches
Drawing upon a 30-day email retention policy and the sent dates of emails, research in the public domain has suggested that the DNC emails were likely acquired on dates between May 19-25, 2016 [@steemwh1sks] for some time.
Looking at the sent dates of emails and the last modified dates of the email files in the first two batches (those with last modification dates in May, two months prior to initial publication) it is possible to determine that:
We can’t, however, make any declaration on exactly when the files were moved to a USB device as different types of copy operations could produce the same result even if the files were transferred to USB weeks after acquisition (as it’s possible to retain the last-modified dates in various circumstances).
Interestingly, the FAT file system indication is in line with claims made by Craig Murray that were published in December 2018 in relation to how WikiLeaks had obtained the DNC leaks through a physical hand-over of the emails.
This particular characteristic was also reported on recently (February 13, 2019) in an article authored by William Binney and Larry Johnson titled “Why The DNC Was Not Hacked By The Russians“. In the article they state:
This data alone does not prove that the emails were copied at the DNC headquarters. But it does show that the data/emails posted by Wikileaks did go through a storage device, like a thumbdrive, before Wikileaks posted the emails on the World Wide Web.
This fact alone is enough to raise reasonable doubts about Mueller’s indictment accusing 12 Russian soldiers as the culprits for the leak of the DNC emails to Wikileaks. A savvy defense attorney will argue, and rightly so, that someone copied the DNC files to a storage device (Eg., USB thumb drive) and transferred that to Wikileaks.
(The article also covers conflicts between intelligence community assessments and Mueller’s July 2018 indictment.)
Looking at the transfer speeds on these batches also gives us reason to doubt that this was a local machine or local network transfer straight to a USB device as the transfers appear to have been at a rate of ~3 megabits/second.
This suggests the files published by WikiLeaks may initially have been transferred remotely.
Some will argue that this supports assertions regarding the DNC being hacked, however, the rates observed alone could just as easily be argued to support statements made by Seymour Hersh that were reported on in July/August 2017 which suggest that WikiLeaks obtained access to a password protected DropBox where the files [DNC and Podesta emails] had been placed.
As well as the batches of emails with last modified dates before the initial publication of DNC Leaks on July 22, 2016, there were two further batches of DNC emails that were made available on WikiLeaks site at later dates and that had last-modified timestamps in August and September 2016.
The third batch, with last modified dates of August 26 2016, also appears to have been transferred via a USB storage device between acquisition and publication.
The fourth of these with last modified dates of September 21 2016, did not have the same 2-second rounding artifact.
While the new tranches included additional DNC staffers, WikiLeaks did not update their web page to reflect that additions were made. However, publication of the batch with the last modified date of September 21, 2016 was announced via the WikiLeaks Twitter account on November 6, 2016 (or November 7 on my side of the Atlantic):
— WikiLeaks (@wikileaks) November 7, 2016
The DNC emails page on WikiLeaks was updated a little over two weeks later (some time between November 22-25, 2016) with the new total (44,053 emails).
Data & Verification
Raw data for last modification timestamps is available here.
Raw data for the above with send dates included are available here.
(The latter of these has approximately 100 entries less than the former, as some emails lacked headers from which a sent date could be determined).
For those that don’t want to (or don’t have means to) scrape all of the data but wish to do a few manual spot-checks on the data linked to above, you can use your web browser to validate individual dates.
To do this, visit the leak you want to check (on WikiLeaks site), click on the “View source” tab and make sure your browser’s developer console is open, then click on the “Download raw source” link. Your browser should send a GET request for the file (which will be for a URL that starts with “https://wikileaks.org/dnc-emails//get/” and is followed by the email ID).
If you expand the details and check the headers, you will find the “Last-Modified” date there and that is where the last modified timestamps are coming from.
The example below uses FireFox:
This obviously isn’t practical for fully validating all of the data due to the volume of emails and is only referenced here as a simple way to do a spot-check that is accessible to most people and helps to illustrate where these last modified dates are being sourced from.
The evidence suggests that the first three batches of DNC emails were likely to have been transferred via a USB storage device at some stage between acquisition and then subsequently being published by WikiLeaks.
However, transfer speeds observed for the batches with last-modified dates matching the dates of acquisition indicate that they were transferred at approximately 3 megabits/second, a lot slower than we would expect if it were a local or LAN transfer, so the transfer we’re looking at likely involved a remote transfer at some point between acquisition and delivery.
Given that (for the May 23 and May 25 batches) the file last modified times and the internal email sent times are close in many cases, it seems likely that the original emails were copied soon after acquisition. The anomalous time shift between last modification timestamps and the send times of emails (especially for the May 25 batch) raises the possibility that an intermediary on the West Coast (US) may have copied the emails to a USB drive. The time shift can be explained by then copying the thumb drive to local storage, while at a location in London, for example. The (hypothetical) existence of an intermediary doesn’t tell us anything about the individual (or individuals) who originally acquired the emails. Thus, this scenario does not necessarily rule out the possibility of an insider acquiring the emails. If we contemplate the intermediate use of cloud storage, this could have been used as a method to decouple the acquisition of the emails from delivery to another party that subsequently delivered them to Wikileaks.
Credit (and many thanks) to Forensicator for researching, sharing observations, providing the data set, charts and more.