Back to SETEC LABS
The Night We Turned the Internet Back On
By: gh0stwire

To whoever finds this —

I don't know when you're reading this. Could be five years from now. Could be twenty. Maybe things are fine where you are. Maybe whatever's happening in the world right now seems distant and strange from your vantage point, the way old disasters always do once enough time has piled up on them. I hope that's the case. I genuinely do.

What I want to explain, while I still have the clarity to do it, is why we did what we did. Not the technical details — those will look different depending on what decade you're in. What I want to explain is the thing underneath the technical details. The reason.

The country doesn't matter. Or rather, it does matter enormously, but if I name it here, I risk the people who helped us. The volunteers. The ones who installed our software on their phones and activated nodes in their apartments and their shops and their cars and trusted that we were who we said we were. Their names aren't mine to give. So: unnamed country, eighteen hours into a government-ordered internet shutdown. Twenty million people with phones that worked fine as phones but couldn't reach anything outside the country's borders. The BGP announcements had been withdrawn. DNS was dead. The government had instructed the two major ISPs to null-route all international traffic, and the ISPs had complied, because ISPs always comply when governments tell them to. They don't have a choice. The people running them go to prison if they don't. That's how this shit works.

SsSnake got the call from a contact at a press freedom organization. He called me first, I think because he knew I'd say yes without needing to be convinced, and he wanted one yes in his pocket before he started making the harder calls. That's SsSnake. He builds consensus the way a good engineer builds redundancy — quietly, in advance, before the failure happens.

I said yes. He called the others.

We had seventy-two hours before the situation on the ground would make our work irrelevant one way or another. That's what the contact said. Seventy-two hours.

My part was the network layer. I designed a backbone: satellite uplinks providing egress to the open internet, connected by point-to-point wireless links running on frequencies I'd carefully selected — specifically the frequencies that the government's monitoring equipment wouldn't be scanning, based on the specs of the hardware I knew they'd deployed. The directional antennas were small, concealable, easy to aim at a second-floor window from a car parked on the street below.

Ph4ntom sourced the satellite hardware and handled placement. I don't know how. I stopped asking Ph4ntom how he does things years ago. He tells you what he can and leaves the rest in a silence that you learn, after a while, to respect.

n1ghtsh1ft built the obfuscation layer. Our traffic needed to be invisible, not just encrypted. He made it look like broadcast television signals — specifically the kind of low-bitrate video data that bounces around between cable infrastructure all the time. If you were scanning the spectrum, you'd see what looked like signal bleed from a regional broadcast. You wouldn't look twice.

CryptK solved the key distribution problem. Getting encryption keys to our ground contacts without using the internet or the compromised phone network — he found a path through the cellular emergency broadcast system, encoding keys in what appeared to be routine carrier test messages. He called it "adequate." Coming from CryptK, adequate means it was brilliant enough that he felt embarrassed about how long it took him to think of it.

VexNull wrote the client software in forty-eight hours. Four megabytes. One button. It ran on everything. When you uninstalled it, it scrubbed itself clean — no binary, no logs, nothing for a forensics tool to find. VexNull built things that assumed they'd be seized, that assumed someone hostile would take that phone apart looking for evidence, and she built them so that person would find nothing. I think about that a lot. The discipline it takes to build for a worst case you're not allowed to describe to the person you're building for.

d4rkfl0w ran ground logistics from nine time zones away, coordinating with volunteers through the new channels CryptK had built, managing hardware distribution, handling the small emergencies that kept arriving because emergencies don't respect your sleep schedule. He didn't break anything. I want that noted. There is an unofficial running record of operations where d4rkfl0w did not accidentally break something critical, and this operation is on it.

We were operational in seventy-two hours. Three satellite uplinks. Fourteen mesh nodes. Two major cities, three towns.

The throughput was terrible. Maybe two megabits per second shared across hundreds of users at peak load. Texts got through. Small images. Short videos — compressed, blocky, the colors a little wrong. But the outside world could see them. Journalists published them. Human rights organizations attached them to formal documentation. Families abroad got messages that said we're okay, we're together, we're scared but we're okay.

I don't know what those messages meant to the people who received them. I can guess. I had a month once where I didn't hear from my brother and I know what that does to a person. Multiply that by twenty million. Multiply it by the specific terror of knowing the silence is imposed, not accidental.

The network ran for eleven days. International pressure ended the shutdown on day twelve. The government said the maintenance was complete. Bullshit, but fine. We dismantled everything and left nothing behind.

I still have one of the directional antennas. It's in my closet behind a stack of routers I should really throw out. Sometimes I get it out and look at it. It's not impressive to look at. Just a flat panel, gray plastic housing, a little scuffed from being transported in a bag. You'd never guess what it was used for by looking at it.

Two megabits per second. That's what I keep coming back to. Less bandwidth than a video call. And through it, for eleven days, a country that had been sealed off from the world was not entirely sealed off. Not entirely silent.

That's the thing I want you to understand, whoever you are. We didn't do anything heroic. We know networks. We built a network. What made it matter wasn't our technical skill — it was the volunteers who activated nodes in their apartments knowing what would happen if they were found. The people who downloaded software from a stranger and trusted it. The journalists who filed stories from a laptop running four megabytes of software they'd gotten off an SD card passed hand to hand through three intermediaries.

We provided the pipe. They filled it.

I hope you're reading this from somewhere it doesn't matter anymore. I hope the thing that made it necessary seems like ancient history. And if it doesn't — if you're reading this because something similar is happening now, somewhere — then I hope it's useful. Not as a technical blueprint. As a reminder that it's possible. That the people who would silence twenty million other people are never as thorough as they think they are. That there are always gaps. There are always frequencies nobody thought to monitor. There are always four megabytes of code that can fit on an SD card in someone's pocket.

There are always people willing to use them.

Take care of yourself.

— gh0stwire, 2026

Back to SETEC LABS