It is said when you commit a crime, you make 20 mistakes. If you can remember 10 of them, you’re a genius. This means that even the slickest criminals leave a trail of bread crumbs that will trace back to the crime. In the case of the Trump Tower-Alfa Bank-Spectrum Health data transfer mystery, Tea Pain just found a doozy!
We know from public data packets that a Trump Tower data server had mysteriously talked to Russia’s Alfa Bank and Spectrum Health in Grand Rapids, Michigan from May 2016 til September 2016. Funny thing is that for the first couple of months, the “Data Machine” was just idlin’, talkin’ once or twice a day, indicatin’ there was little or no communication goin’ on.
But in late June, 2016, the “Russia Data Machine” kicked into turbo! What changed? What prompted this sudden burst in activity? Tea Pain loaded all the data activity into his trusty SQL server and started slicin’ and dicin’, lookin’ for any clue of what kicked this data buggy into overdrive. Tea Pain summarized all the activity by site and the first clue emerged.
The first thing you notice is that this server was dedicated to do one thing and one thing only, share info with Alfa Bank and Spectrum Health. The “Wholesale Internet KC” transactions were from a IP block wholesaler that was used primarily when this server was set up. That leaves two stray “pings” to account for. The one that instantly jumped out was “OBIT.RU.” A quick browse there will blow your hair straight back!
Obit.RU is a large Russian telecommunications company. Two stray pings and one was from a Russian communications group? They say coincidences take a heap of plannin’!
One of the facts that is not well known about this server is that it was a leased server physically housed in Lititz, Pennsylvania. It don’t take an orbital payload specialist to figure out why Trump Tower chose a leased server, not a managed, physical server in Trump Tower, to host all this treasonous data hanky-panky. This server was outside of the control of the Tower’s day-to-day IT department and would have eliminated gettin’ Trump’s IT personnel involved. Remember, the smaller the conspiracy, the more likely it might succeed.
This machine was most likely administered by an outside tech in order to replicate data among the three sites. Data replication requires a few ports to be opened on a computer’s firewall to allow data to flow in and out. Tea Pain, just like most any other tech has a ritual after changin’ firewall settings. To make sure none of the normal firewall settings get messed up, Tea Pain typically opens a browser or a diagnostic program and send a “ping” to the site to make sure the firewall is workin’ correctly. Whoever logged into this machine that day most likely made firewall modifications and, like Tea Pain, pinged the site from a public machine to make sure everything was functionin’ properly. The big difference? This ping came from Russia…from Obit.RU…by a Russian tech…from a telecommunications company!
So why did Tea Pain go to all this trouble to explain these little details? One thing Tea Pain deliberately held back was the date of this one stray ping. Hold on to your britches…
Bang! We can reasonably assume that a Russian computer tech had access to that server and was makin’ a number of modifications just moments before the replication kicked into high gear! He made his mods, and like a Russian creature of habit, pinged the site to double-check his work. This came just a few weeks after Don Jr’s now-famous meeting with the Russians. The agreements were made, the changes were in place, and Trump’s “Stealth Russian Data Machine” just switched on the “Treason-Drive.”