I’m a network engineer in Nome, Alaska. I work with the government on the Quintillion Subsea Cable Network. I recently discovered an error in our handling of encrypted data across the lines. Basically, the boxes that had been setup at the farthest end of the line were cycling through random number generating seeds incorrectly, creating identical seeds, and therefore OTP keys, every 65,536 iterations. In my research of the issue I decided to run a double-pad attack against what I thought was arbitrary connection information. The result of the decryption was a series of messages I have come here to share. I don’t recognize most of the jargon being used, and I don’t know what type of end-point this came from. I have top secret clearance, but not the appropriate TSSCI required to be involved in the endpoints, so essentially, I don’t need to know and have never asked. I share this information under great risk. I hope somebody here can give me some answers.
IIIIIIIIIIIIIIII INDUSTRIES May 23, 2017 Incident #0004245
At 06:00, personnel in Zone D reported seeing bright red flames hovering in thick clouds due south of main facility. By 0630, a total of five actors from three contiguous zones, D through F, independently confirmed the presence of floating flames. Reports indicate that the flames had a base somewhere in a network of rain clouds described as “black or purple” in tone. Operators intercepting the calls described the attitudes of reporting personnel as “aggravated.” Response teams were dispatched from main facility at 06:35. All team members were informed that organisms encountered were to be considered contaminated by substances unknown. Authorization was given by acting Ward Supervisor to dispose of personnel assigned to Zones D, E, and F, upon contact. Emergency containment crews were dispatched from main facility at 06:40. All containment crew members were directed to utilize HAPR protocol and available resources to determine the nature of the phenomenon, and if possible, contain it. A Holding Review was initiated at 06:45 in containment facilities Gamma and Delta. At 07:10, Control received reports from both facilities that no subjects appeared to be involved in the phenomenon. At 7:20, emergency containment crews reported the phenomenon has dissipated. Zones D, E, and F, were neutralized and being prepared for full response analysis. Precursory tests showed elevated levels of Argon and Oxygen. Full results of the analysis are forthcoming. Please see attached documents for further information.
IIIIIIIIIIIIIIII INDUSTRIES May 23, 2017 Incident #0004246
At 13:20, containment facility Gamma notified Control that subject #00189 was no longer in containment area. At this time full facility lock down was initiated. Emergency containment crews were dispatched from main facility to secure surrounding areas. Investigation was initiated by acting Ward Supervisor at 13:25. At 13:55 the Directors were alerted to the escape. Due to the physiological nature of 00189, recovery is unlikely. Investigations are ongoing. Please see attached documents for further information.
IIIIIIIIIIIIIIII INDUSTRIES May 24, 2017 Incident #00014245
At 06:00, containment facility Gamma notified control that subject #00189 was discovered inside its containment area. No explanation has been given for the failure of the previously adequate containment methods used for 00189. At 6:05, containment crews were assigned to 00189’s cell, armed with HAPR conforming methods of containment. An analysis of the moisture resistant polymers inside the cell were initiated at 06:20. Mobility of 00189 was temporarily restricted via a lowering of humidity inside containment area at 6:25. Please see attached documents for further information
IIIIIIIIIIIIIIII INDUSTRIES May 24, 2017 Incident #00014246
At 08:15, containment facility Gamma failed to respond to request of status from control. Response plan G initiated at this time. Remote response teams were called from IIIIIIIIIIIIIII and IIIIIIIIIIIII at 08:25. Control is at this time under lockdown. Acting ward supervisor and control staff on duty are restricted to main office in control. As of 08:30, all communications to control ceased. Response plan I initiated at this time. No confirmation from the Directors received. Analysis of peripheral monitoring devices show an increase of temperature in holding facility Delta of 3.8 degrees. Investigation is underway. Please standby for further information
IIIIIIIIIIIIIIII INDUSTRIES May 24, 2017 Incident #00014245.1 Analysis of peripheral monitoring devices show a further increase in temperature in holding facility Delta of 14.5 degrees. As of 09:20, control continues to experience radio silence. We operate under the assumption of catastrophe. Please standby for further information.
IIIIIIIIIIIIIIII INDUSTRIES May 24, 2017 Incident #00014245.2 10:00 Please respond.
IIIIIIIIIIIIIIII INDUSTRIES May 24, 2017 Incident #00014245.3 11:00 Please respond
IIIIIIIIIIIIIIII INDUSTRIES May 24, 2017 Incident #00014245.4 As of 11:35, all peripheral monitoring devices have ended transmission with control. We operate in with no information. Final transmission from all devices show growing deviation of a cyclic nature. Please standby for further information.
IIIIIIIIIIIIIIII INDUSTRIES May 24, 2017 Incident #00014245.5 12:00 Please respond.
IIIIIIIIIIIIIIII INDUSTRIES May 24, 2017 Incident #00014245.6 01:00 In accordance with response plan I, all control staff have begun self-termination. Forgive my breach of protocol, but I have to say it’s been a pleasure working with you gentleman. If anybody receives this, tell our families we died as patriots.