KX-series security droid

"Still resisting? Unwise."

―A KX-series security droid^[14]

KX-series security droids,^[1] also known as KX-series enforcer droids,^[3] KX enforcer droids,^[18] KX units,^[19] KX droids,^[20] or executor droids,^[21] were a model of security droid manufactured by Arakyd Industries that was in service to the Galactic Empire during the Galactic Civil War.^[1]

Description

"KX droids have a long range of combat capabilities, excellent probability analysis algorithms, and direct access to the Imperial datanet."

―R0-GR^[20]

KX executor droids had an intimidating stature.

KX-series enforcer droids were a model of security droid manufactured by Arakyd Industries for the Galactic Empire. They had a black-colored body designed with exaggerated human proportions but with the mobility of a human athlete. They were able to operate a variety of tools, equipment and weapons and could carry gear without becoming exhausted, such as a blaster.^[9] Their size and strength made them intimidating and unsettling to many people, both Imperial and rebel alike.^[22] The shell that encompassed the droids cognitive module in their head,^[9] as well as their fists,^[23] was made out of carboplast-composite. Their upper legs had shock absorbing struts and their ring joints in their knees included a servo driver. Complex gyro-balance system kept them walking upright. They came equipped with a built-in comm package, recharge port, and a data spike hidden in their fist that allowed them to connect with standard communication frequencies for areas they were assigned to. The Imperial crest was imprinted on the side of each shoulder,^[9] one of which could be emblazoned in gold if the droid had received an enhanced status.^[24]

While the Imperial Senate had prohibited the creation of battle droids, Arakyd used a loophole in the law by marketing the KX-series as "security droids." They were programmed without the standard restriction against harming organic sentient lifeforms. The droids were programmed to recognize and defer to Imperial Military officers ranked lieutenant or higher.^[9] KX units were also equipped with chest-mounted olfactory sensors, providing the security droids with an efficient "sense" of smell.^[13]

The KX-series droids were programmed to speak and interact with people, but were not as proficient at it as protocol droids were. They could handle a wide range of tasks, including escorting dignitaries, protecting important people and defending Imperial installations.^[2] However, they could also fail to understand certain statements by processing them as orders meant to be taken literally.^[25] Nevertheless, Baron Espis Zanchal owned a service droid that resembled^[26] the KX.^[7] Beyond security purposes, KX-series droids could serve in manual labor and translating, although the droids' programming made them find these tasks tedious. KX-series droids were pre-programmed in the operation of more than forty Imperial transport vehicles, but were capable of quickly adapting to new ones.^[22]

The Security Droid Enforcer was more challenging in combat than a standard KX-series security droid.

A variant of this model existed by 9 BBY,^[27] known as the Security Droid Enforcer, sporting tan plating rather than black. Like some scout troopers, these counterparts were equipped with electro riot batons, combined with a reinforced chassis, making them far more dangerous than the standard model. They were primarily designed to train stormtroopers in the use of the electrobaton.^[12] One service droid model used the modified head of a KX-series unit.^[28] That same modified head design was used in a monster droid model.^[29]

History

Encounters with a Jedi

"Visitation is not permitted."

―A KX-series security droid, to Cal Kestis^[14]

A large group of KX-series security droids from the Imperial garrison of Ilum was destroyed by Jedi Cal Kestis.

The droids were deployed as early as 18 BBY,^[30] and served high-ranking Imperials.^[24] They were also used to guard Imperial installations, such as the Imperial Refinery in Kashyyyk, the mining headquarters on Ilum and the Fortress Inquisitorius on Nur. During his mission to Ilum to find a kyber crystal and build a new lightsaber, the Jedi Cal Kestis confronted and destroyed a large group of these droids.^[14]

In 9 BBY, K-4O5, a Security Droid Enforcer, led Kestis to Imperial Senator Daho Sejan on Coruscant. Kestis faked a capture to get closer to the senator and his starship, on which Sejan had stored Imperial military information, which Kestis intended to deliver to Partisan Saw Gerrera. K-4O5 found Kestis again after his escape and confronted him. The droid was destroyed in the fight with Kestis and his ally, Bode Akuna.^[12]

Rebels and other insurgents

"I have carried out many Imperial directives prior to my reprogramming. Killing, maiming, kidnapping, arson, telemarketing. My orders were usually intended to do harm to the Rebel cause, is that what you mean?"

―K-2SO, during a mandatory psychological check-in^[31]

A KX-series security droid was present on Corellia among a trio of stormtroopers during the heist on Corellia.^[32]

A KX-series security droid accosts Cassian Andor near Arkie's, on Pier Nine on Niamos.

In 5 BBY,^[33] several KX droids were stationed on the beaches of Niamos alongside coastal defender stormtroopers^[25] during the Imperial occupation.^[34] Six KX-series security droids participated in the Ghorman Massacre, where they were used by the Empire against protesters demonstrating against the Imperial presence on the planet. One of those units^[35] was designated K-2SO,^[7] who was damaged after Ghorman Front operative, Samm, hit it with a vehicle, and salvaged by rebel agent Cassian Jeron Andor,^[35] which would lead to K-2SO's reprogramming^[36] and service against the Galactic Empire.^[7]

During the Galactic Civil War, they were present on both Jedha and the Imperial facility on Scarif.^[7] K-4D8 was an example of these droids.^[24] At least one KX-series security droid was stationed aboard an Imperial II-class Star Destroyer.^[37] Around 1 ABY,^[38] the astromech droid R2-D2 staged a rescue of his friend C-3PO from the vessel, creating utter chaos throughout the ship. Aware that the attacker was a droid that had incapacitated several squads of Imperial forces, a trio of stormtroopers searching for the culprit cornered the KX-series security droid and, despite its protests, opted to destroy it.^[37]

Also around that time,^[39] a KX-series security droid was among the forces that detained Doctor Chelli Aphra and her crew on Skako Minor. Caught in an explosion caused by a Flufto, one of Aphra's genetically-modified tookas,^[40] the droid was destroyed but auto-transmitted footage of the events unfolding upon deactivation. The footage was captured by Imperial scanners and was sent to Inspector Magna Tolvan, having tripped several active search filters set by Tolvan. Tolvan and a corporal reviewed the posthumous transmission and associated location data, providing them a lead on Aphra's location.^[41]

A machine with the head and torso of a KX-series security droid was constructed by the Tarkin Initiative but ultimately frozen and put into storage aboard Hivebase-1, where it was found by Aphra, her crew, and Hera Syndulla.^[42]

Threats from within and without

In 3 ABY,^[38] a KX-series security droid was present aboard the Imperial II-class Star Destroyer Executor. When bounty hunters Boba Fett and Beilert Valance infiltrated the destroyer in an attempt to rescue the carbon-frozen Han Solo, the droid approached the pair and lifted Fett off his feet. Valance damaged the enforcer's head with his a shot from his palm blaster, causing it to question whether Valance himself was a droid before the cyborg fired a second blast, incapacitating the Imperial machine for good.^[43]

At least two KX droids who managed to think for themselves were part of the Second Revelation.^[15] Two KX-series security droids were present in the city of Kantiema on Brentaal IV at the time of the bombing orchestrated by Jul Tambor and caught in the ensuing blast.^[44] Another two KX droids were among those formerly wronged by Darth Vader and rebuilt in an effort to take revenge on the Sith Lord as part of the droid uprising.^[16]

KX-series security droids and DT-series sentry droids infected by Scourge on Ryloth.

Sometime after the Battle at Amaxine Station, four of these droids were transported to the Amaxine Space Station aboard a Sentinel-class landing craft to aid in the cleanup effort ordered by the Emperor himself. One of the units became infected after picking up a disk containing the Scourge, a being born of the Spark Eternal^[8] and a droid dropped by the Fermata Cage.^[45] Upon returning to an Imperial I-class Star Destroyer, the Scourge used the KX to spread itself, overwriting all droid life aboard and leading them in a murderous uprising against the organic crew. The security droid, the disk that corrupted it perched on its shoulder, later stared out the viewport on the destroyer's bridge, the Scourge reflecting on its vast knowledge, insight into the galaxy, and plans for omnipresent dominion.^[8] The Scourge used a number of KX units as bodies on the Star Destroyer^[46] and began to carve into one to alter the droid's body.^[47]

Waning Empire

KX-series secruity droids were deployed to the surface of Mandalore with E-22 reciprocating double-barreled blaster rifles in the "Night of a Thousand Tears."

Between 4 ABY and 5 ABY,^[48] KX-series droids armed with E-22 reciprocating double-barreled blaster rifles were deployed to the surface of^[11] the besieged^[49] world of Mandalore,^[11] a world which had long resisted Imperial rule^[50] and, in response, was targeted^[51] with a "Great Purge" to exterminate the Mandalorian people. In the so-called "Night of a Thousand Tears," after Imperial TIE/sa bombers had wiped out^[11] Mandalorian cities,^[52] KX units picked through the wreckage and eliminated any survivors they uncovered with the help of viper probe droids.^[11]

Imperial Refining Platform M36 hosted no organic life-forms, and was instead guarded solely by KX-series security droids armed with E-11 blaster rifles and T-21 light repeating blasters. The platform's security force was dispatched by Jedi Knight Luke Skywalker when the Rebellion launched a raid on the facility.^[10]

Beyond the Empire

Following the defeat of the Empire, the New Republic elected to use the KX-series for its own security.^[17] In 9 ABY,^[53] the modified KX-series security droid K-A0S participated as a Hunter in the Hunters of the Outer Rim competition on the planet Vespaara.^[54] Decades later,^[55] the B1-series battle droid-turned-author R0-GR recorded details about the KX-series security droid in his "droidography."^[20]

Behind the scenes

KX-series droids were developed for the Star Wars anthology film Rogue One: A Star Wars Story. Their first canonical appearance was in Star Wars: Commander. They later appeared in the ambiguously canon Star Wars: Visions.

The following section contains information from Star Wars: Visions media that was referenced in no other canon source. Lucasfilm has stated that Visions stories and their related media are not required to "tie into the larger chronology" of Star Wars storytelling. Editor discretion is advised.

At some point between 1 ABY and 5 ABY, a KX droid accompanied an Imperial officer when he raided a club on the occupied world B-bel to intimidate Loi'e, but the rebels were able to escape.^[56]

Star Wars: Visions information ends here.