It has come to our attention that sometime near the turn of the 21 st century, the Traxus AI was assaulted via a Trojan horse. The malicious system was able to lie dormant in the network for inconclusively long period of time before it was detected. The errors were initially noticed yesterday afternoon, at around 16:00 hours, when the Traxus AI fell into disagreement with another Artificial Intelligence during routine congruence testing. The errors were then isolated to the Traxus AI following further congruency tests with several other Artificial Intelligence systems. Damage reports are inconclusive, fellow networks estimate that up to fifty percent of the Traxus mainframe may have been damaged. The malicious code has embedded itself so deep within the network that most of it will have to be removed by hand. Upon isolating the errors to the Traxus super computer, fellow AI’s have forwarded this message to everyone bearing association with Traxus.

The good news is, we’ve been able to hold our ground as far as containing the infection within the Traxus network. We have received distorted transmissions from Traxus indicating that he is now aware of his present situation, however without an adequate damage report we are unable to decipher whether this is in fact Traxus, or the manipulate code.

The following list is a post notification event log of scans and attempted repairs to the system. (Click to read log)

Logic Engine Checkup - 01:00 hours from notification.