24 May 2888, 02:15PM PST

TRAXUSCONNECT

NinoDC_0312: @TOI_Board The situation with Interorbital United Shipping continues to escalate. Recent intel suggests their exploration into reopening old routes is top concern.

KrisBD_4505: Steps?

NinoDC_0312: Multi-phase contingent underway.

KrisBD_4505: Possibility of added clarity in United Shipping’s intentions? What is our confidence in current intel?

NinoDC_0312: Confidence high. Timeline matches long-run surveil interests related to Project: GOLIATH. Clarity in the works with @UrosBS_0111’s aid.

UrosBS_0111: United Shipping new route operation is a priority. Further insight into current data sets is passphrase protected, but we are looking for workarounds.

UrosBS_0111: Status is: Passphrase is scattered—traces rumored across the net. We have netcrawlers actively searching for the pieces, and the path to the originating terminal itself. Once path is ID’d and passphrase assembled we believe we will have access to enough connected data to understand and address United Shipping’s intentions.

HedvT_6221: If this terminal’s OS is a backdoor around United’s infosec and this backdoor is known to the point of rumor how can we be sure it won’t be sealed with deeper layers of security before we can glean the necessary details?

UrosBS_0111: We are moving forward confident in our ability to secure our interests before United can adjust their infosec response. Or field countermeasures.

KrisBD_4505: Is this effort in-house or freelance?

NinoDC_0312: Initial efforts to access the intel in question are being handled in-house by Uroš and their team. Additional measures utilizing freelancers are being set up to act on our findings.

UrosBS_0111: We may enlist outside help to track/crack the phrase. Will update as we proceed.


— everything above is 1:1 source · from chats · karnemir ↗

Cited by

Project Goliath · Traxus · Vulcan