In Rogue One: A Star Wars Story, Cassian Andor leaves fans shocked as he kills his own informant, Tivik, moments after receiving critical intelligence. It’s a jarring introduction to the Rebel spy and touches the vein that the fight against the Empire wasn’t always clean. But why did he do that? Here’s a breakdown.
Here’s why Cassian Andor had to kill Tivik in Rogue One
In Rogue One: A Star Wars Story, Cassian wasn’t just a Rebel soldier; he was an undercover operative who had been deep in the fight for most of his life. When he met Tivik at the crowded Ring of Kafrene station, it was to collect intel about a mysterious Imperial project. Tivik, clearly rattled and injured, told him what he knew: the Empire was building something massive, later revealed to be the Death Star.
But before Cassian could process it all, stormtroopers arrived. He took them down quickly, but the noise had already drawn more attention. With his injured arm in a sling, Tivik admitted he couldn’t climb to safety. Cassian realized in that moment that there was no escape for them both.
If the Empire had taken Tivik alive, they could have caused catastrophic consequences. He was panicked, injured, and carrying sensitive information. Under Imperial torture, he would almost certainly break. The Empire would uncover the details about the Death Star, the Rebellion’s movements, and Cassian himself. Knowing this, Cassian made the painful decision to eliminate the risk. He reassured Tivik with a quiet, “We’ll be all right,” then shot him from behind, killing him.
Andor Season 2’s finale bridges the gap between the series and Rogue One, with Cassian receiving a message from Tivik. This meeting directly sets up the opening, reinforcing how high the stakes were. Tivik’s death wasn’t just a random arc. It was an important scene that shaped Cassian’s path toward stealing the Death Star plans.
