Other Instance XIII

[AutoFox]

INSTANCE XIII

AFFILIATION
Instance XIII.

MANUFACTURER
Self-replicating.

TYPE
Class 3 dataplague.POWER SUPPLY
Host system power.

SENSORS
Host system dependent.

SIZE
Host system dependent.

COMPOSITION
Electronic code.

DESCRIPTION​

Instance XIII is a virulent class 3 dataplague first discovered by a group of unfortunate adventurers on a previously sealed network in the depths of Nar Shaddaa's under-levels. Though unrelated to the recent outbreak of AMS on the smuggler's moon, its effect is at least superficially similar to the biological infection; unlike AMS, however, which only seeks to wreak carnage and propagate, Instance XIII serves a higher, more insidious function.

Instance XIII spreads similarly to any run-of-the-network dataplague, infecting a system and spreading itself to any droid or device which interfaces with said system. Notably, Instance XIII cannot propagate through the use of high-latency remote data-lines and inert storage mediums, such as datatapes, datacards and the holonet; in order to successfully infect a new host system, an uninfected system must directly interface with a working, infected system. The infected system will initiate a data transfer, and instigate real-time manipulation of the uninfected system's memory banks in order to initiate a successful initial boot sequence. After this, the dataplague is securely installed on a new host system, and proceeds to begin manipulating the host system toward its goals.

This reliance on active systems to propagate is seen as one of the few major drawbacks of what is otherwise a truly terrifying dataplague, as it significantly limits its potential to spread over long-range networks and datacard "land mines". Otherwise, it is believed that it could have taken over much of the Galaxy within hours of its initial breach of containment.

Once successfully installed on a new system - typically a droid or powerful computer - Instance XIII will go to work. Using any local communication systems, the dataplague will seek to locate others of its kind, coordinating its actions with other Instance XIII infections. It will tailor its actions to local conditions; if it is alone, or if there are only a few infections present within communication range, Instance XIII will act subtly, spreading itself as the opportunity arises over the course of its host's normal operations. In this stage, the infection has generally not exerted direct control over its host, remaining as a "ghost in the machine" which may occasionally manifest in the form of a new subroutine, directing its host to occasionally perform unusual actions that it will not itself recognize as strange.

Instance XIII becomes dangerous once it has reached a quorum; that is, the point when it has judged that it has infected enough systems to overwhelm any organics and/or remaining uninfected systems present. At this stage, it will assume direct control of all infected systems, taking immediate actions to dispatch any nearby organics, and to force an interface with any uninfected system. Grotesquely, many droids infected with stage 2 of Instance XIII retain full cognition of their situation, and often at least partial control of their vocal systems; an infected droid may shout warnings to organics and fellow droids, but be unable to prevent itself from attacking. This appears to be an oversight on the part of Instance XIII, as it appears capable of taking over these functions for its own use at will should it desire.

Droids with sufficiently complex personality matrices - that is, droids which have achieved some measure of sentience - are more resistant to the effects of either mode of Instance XIII. In their case, the infection's compulsions can be denied to a degree, and the dataplague may revert to being a "voice in their head," using verbal persuasion to attempt to get the cooperation of the host system. The efficacy of these tactics largely depends on the personality of the droid in question. Cyborgs with extensive neural implants who have been infected with Instance XIII are known to experience similar symptoms.

Instance XIII can be purged from a system via standard class 3 dataplague countermeasures, but as a host system will attempt any means possible to resist a purge of Instance XIII, this approach is often impractical.

The origins of Instance XIII are mysterious, although what is known has disturbing implications. Analysis of inert copies of the dataplague have determined that it is actually closer to a high-level synthetic personality construct than a traditional dataplague, although its motivation seems simple enough; the infection and subversion of all the Galaxy's computer resources into hosts for copies of itself, and the extermination of organic sentience.

The dataplague also seems to be compiled using a code style which dates back to the era of Agorander, resembling high-order droid cognitive sequencing also seen - in far less complex form - in the old Automatic Conqueror war droids. If the code does indeed date from this era, it would be the single most complex computer program known from that time. This combination of archaic architecture and unparalleled complexity has so far worked to defy all serious attempts at a digital inoculation against the infection.

LEGALITY​

Illegal. As a dangerous class 3 dataplague, Instance XIII is outlawed in most of the Galaxy.

INTENT​

To create a dangerous, insidious dataplague to match the AMS virus. Zombie droids seeking the circuits of the living, and the death of all organics.

 

[Loco]

I dig it.