DEF CON: How a Going-Away Party Became the World's Largest Hacker Convention

In 1993, Jeff Moss, better known as The Dark Tangent in hacker circles, was leaving Las Vegas. A friend was moving away too. The local computer bulletin board system community was scattered, the scene was changing, the era of local dialup networks and modem pools was coming to an end. Before everyone dispersed completely, Moss decided to throw a party. A going-away party for the local scene. He expected maybe a hundred people.

He rented the Flamingo Hotel. Set up some conference tables. Put out flyers on the local BBS systems. Called it DEF CON because he was literally turning the dial down on the computer modems, reducing the confer mode from full defense condition to minimum.

Over a thousand people showed up.

What happened on that weekend in the Flamingo would become the origin story of the most important gathering place in hacker culture. Not the first hacker convention. But the one that refused to become legitimate. The one that never turned into a corporate conference. The one that kept its roots in the underground even as it grew into something massive.

The First Gathering

The original DEF CON was chaos in the best sense. People showed up. There were talks, but not many, and not particularly organized. There were contests, including the one that would become legendary: Spot the Fed. The premise was simple. Law enforcement would send undercover agents to the conference. If you could identify them, you won a t-shirt. It was partly a joke, partly a real safety measure for a community that had legitimate reasons to be paranoid about federal surveillance.

The Spot the Fed game was iconic because it captured something essential about the early hacker community: the belief that law enforcement was actively infiltrating the scene, that paranoia was rational, that identifying threats was both serious and fun.

Badge hacking started early too. The DEF CON badge became an object that could be modified, reprogrammed, turned into something other than what it was designed to be. This was the hacker impulse in microcosm: take a tool designed for a specific purpose, understand how it works, and make it do something else.

The Wall of Sheep came later, but when it did, it formalized something that had always been implicit at DEF CON. Network passwords displayed on a screen for everyone to see. Not as a lesson in security, but as proof that the people at the conference could break it, capture it, display it. The Wall of Sheep was humiliation and learning combined.

And then there was Capture the Flag, the hacking competition where teams competed to break into systems, solve puzzles, find flags hidden in the network. This brought the competitive element, the sport of hacking, into physical space where it could be watched and celebrated.

All of this happened because Moss had the instinct not to turn DEF CON into a corporate conference. Many hacker gatherings of that era did exactly that. They got legitimate, got corporate sponsorship, got speakers from major companies and government agencies. They became respectable. DEF CON did the opposite.

The Physical Culture

There was something about gathering in person that the digital world couldn't replace. The bulletin board systems of the 1980s had created a community of people who had never met, who had only interacted through text on screens, through phone calls to modems, through the purely digital. DEF CON gave them a place to be physical, to be in the same room, to recognize each other.

It created rituals. The black t-shirts. The badge. The hotel takeover. The culture of presentations that were not always professional but were always technical. There were official talks, but there were also impromptu hallway conversations between security researchers, exploit developers, system administrators, and people who just wanted to be around others who understood that systems were made to be understood.

Las Vegas was perfect for this. A city built on the idea that normal rules don't apply, that what happens here stays here, that you can reinvent yourself in the desert. DEF CON thrived there because the city itself was weird enough to contain a conference full of people breaking into things and talking about it openly.

The conference grew every year. A hundred people became five hundred, became a thousand, became a few thousand. By the 2000s, DEF CON was drawing six, seven, eight thousand attendees. It had become a rite of passage for anyone serious about security. If you were in the hacking world, you had been to DEF CON. If you hadn't, you aspired to be there.

The Tension

What made DEF CON complicated was that it stayed underground even as it became mainstream. The conference grew huge, but it maintained a culture of mischief, of rule-breaking, of treating corporate security as a challenge. This created tension.

DEF CON invited speakers from security companies, from government agencies, even from the FBI and NSA. It was part of the conference's unique position: it was a place where law enforcement and hackers could meet on neutral ground, could understand each other, could even collaborate. But this legitimacy was held in constant tension with the conference's roots in illegality, in breaking things, in treating established security as permission to try harder.

The corporate sponsorships grew. Major tech companies paid for booths, for official tracks, for the visibility of being associated with the conference. This was good for the conference's finances. It allowed the conference to grow, to host more people, to bring in more speakers. But it also created the risk that DEF CON would become just another corporate conference with a hacker aesthetic, a place where tech companies went to recruit and sell products.

That tension defined the 2010s and 2020s at DEF CON. How do you maintain the underground ethos while operating at corporate scale? How do you keep the culture of breaking things alive while hosting vendors who depend on things not being broken? How do you honor the original spirit of the conference while it's grown into something that the original organizers could not have imagined?

What It Created

But DEF CON did something that could not have happened any other way. It created a permanent gathering place for the hacking community. Not a virtual place, but a physical location where, every year, thousands of people came together. It created traditions that lasted decades. It created a space where you could present research that was technically illegal in some jurisdictions, and do so openly, in front of hundreds of people.

DEF CON made hacking into something visible, something that could be celebrated, something that could be studied. It brought together the underground and the mainstream. It proved that there was enough interest in security, in networks, in understanding how systems work, to sustain a massive annual conference.

It also created a pipeline. People went to DEF CON, learned about security, learned about the cutting edge of the field, got connected with others, and either entered the field professionally or went deeper into the underground. The conference became both a gateway into legitimate security careers and a gathering place for people pursuing deeper knowledge outside those official channels.

The Legacy

DEF CON still happens. Every year, thousands of people descend on Las Vegas for a weekend to present research, compete in contests, meet peers, and engage in the strange ritual of trying to find federal agents in a t-shirt. The conference has changed. It's more professional. It has official programming. It has corporate sponsors. It has security measures that the original conference never needed.

But the spirit is still there. The culture of curiosity, of trying to understand systems by breaking them, of respecting technical depth regardless of how you use it. The conferences where actual exploits are discussed. The competitions where teams are trying to break security systems on the spot. The badge hacking, the Wall of Sheep, the endless hallway conversations between people trying to understand the same systems from different angles.

What Jeff Moss created, even if by accident, was a physical instantiation of the hacker community. A place where the underground could gather, where culture could be formed and reformed, where new people could enter and learn the traditions. It was a going-away party that never ended.

That's worth something. That's worth a lot, actually.

DEF CON taught the hacking community that it was big enough, significant enough, culturally important enough to have its own gathering place. That lesson changed everything that followed. It showed that there was power in meeting in person, in creating shared rituals, in building community around the shared value of understanding systems deeply.

The conference is still running. Still in Las Vegas. Still a thousand times bigger than the original party. Still, in some sense, that same goodbye gathering, except it never said goodbye. It just kept going.

That's what it means to have a place where the people who bend systems can meet, celebrate, compete, and teach each other. That's what DEF CON became. That's what it still is.