October 16th, 2017 started off like any other Monday. I awoke at 6 a.m. and drove to the YMCA to play racquetball, ready to start the week with a win.
When I finished playing, I tweeted out a cute quip:
I then hit the steam room and the shower to relax and freshen up. Upon returning to my neighborhood, I encountered an unusual problem: a police cruiser with its lights flashing was blocking the entrance. I came to a stop and rolled down my window:
"Hi Officer, is there a problem? I'm just trying to get to my house."
"Sorry, we have to secure the area due to an ongoing incident."
"Is it an active shooter?"
"Unclear, but we have information that he has long guns on the premises."
"Well shit, what should I tell my family to do? They're at the house."
"Call them and tell them to get in the car and exit the community."
I pulled off the main road and found a place to park so that I could call the house.
"Hey, don't panic but the police are locking down the neighborhood due to an incident. You should get in the car and leave."
"OK, I'll be right out."
I waited a few minutes and then received a call back.
"The police stopped me as I was leaving and asked me if I was OK. Apparently they were called to our house! They want you to come speak with them at the mobile command unit around the corner."
I drove back to the entrance and told the patrol officer that his captain wanted to speak with me, so he waved me through. Upon entering the mobile command unit, the first thing I was asked was:
To which I replied:
It wasn't long before the news stations showed up; apparently, they didn't even know what "swatting" meant.
The news stations managed to get a copy of the phone call that was made by the attacker; you can listen to it here. The attacker claimed that they shot and killed someone and were holding others hostage after rigging the front door with explosives.
Once the news crews left and everything calmed down, I figured I should let the attacker know that they failed to achieve their goal.
Within a few hours of making my tweet, I received a threatening voicemail from a number with a New York area code; you can listen to the voicemail here. Note a common theme between the 911 call and the voicemail — both times he demands $50,000 (or the equivalent in BTC.)
Within 48 hours the Durham Police Department told me that they had traced the call to a throwaway server in Texas but hit a dead end and were turning the case over to the FBI. I never heard from the FBI. I lost any confidence in the ability of law enforcement to protect me a long time ago, so this was disappointing but not surprising.
What did I do in response? I installed 360-degree 4K resolution surveillance around my property, double-checked the rest of my physical security setup, took a few firearms out of the safe, and I waited.
Fortunately my intuition that the attacker didn't have the guts to put his own life in danger by physically attacking me proved to be right. There were no further (physical) incidents.
Shit just got real
Swatting is not a game; it can be fatal. Case in point:
I have little hope that the perpetrator will be found, but I feel compelled to offer an additional incentive.
I want to make it extremely clear that I will not tolerate threats against myself or anyone I care about. I will defend myself and my loved ones until my dying breath with every resource at my disposal.
There was a lot of speculation that this was related to the bitcoin scaling debate, but the attacker never said what his motivations were. After the fact, he left me this voicemail demanding a ransom payment… but didn't even give me an address to which I should send the BTC!
After speaking with other folks who have been harassed, I fully expected other annoyances such as:
- Using stolen credit cards to purchase things and ship them to my house.
- Purchasing drugs / illegal things on darknet sites and shipping them to my house.
- Tampering with the accounts for my utilities to get them turned off.
- Forging a deed in an attempt to claim ownership of my home.
On November 9, I got email bombed by a bot that was signing me up for a ton of email marketing lists.
Since the emails were "legitimate" marketing rather than mass emails from a few sources, I decided pretty quickly that the best option was to just I turn off my email for the day and made most of the signups bounce, preventing my email address from getting added to the lists of the marketers. Having 8 years of experience writing email marketing software has its perks.
Twelve hours later statoshi.info was DoS attacked and my host blackholed the IP address to save their own infrastructure. No big deal.
I've kept this detail a secret for the past year, but I wasn't home when the attacker sent the SWAT team to my house. I truly hope that the perpetrator reads this article and gets to realize how miserably they failed.
I highly suspect that the reason the attacker chose to strike when he did was from the tweet you see at the beginning of this article. I generally vary my social media posts and delay tweeting anything that may tie me to a specific location.
So, when the attacker saw that I "just woke up" he incorrectly assumed that I must be at home – he was clearly not sophisticated enough to know my routine. I can only imagine how this story may have played out differently if not for this one tiny point.
Had I been home, we may not have made contact with the SWAT team until they were breaking down the door, which would have likely ended badly.
The real problem with swatting
I've waited so long to reveal the details of this day because I wanted to take additional steps to improve my operational security. I've written down all of the precautions I've taken over the past year and intend to publish them soon.
The thing is, I was lucky that the Durham Police Department is more competent and cautious than other departments in the U.S. Had a few variables been different that day, I could easily be dead.
While I certainly blame the attacker for the actions they took, my root cause analysis places the blame squarely upon law enforcement for creating an exploitable vulnerability. The militarization of police combined with non-existent authentication creates a great environment for swatting.
When you think about it, the asymmetry is disturbing – a single anonymous phone call can result in lethal force being deployed in a matter of minutes against an arbitrary target. A single anonymous phone call costs only a few dollars to make and yet can consume tens if not hundreds of thousands of dollars in public resources just to determine whether or not a threat is real.
What's the solution? While I'm a huge privacy advocate, I don't think it should be possible for someone to deploy lethal force with no risk to themselves. At the very least, you should have to put your reputation on the line so that you can be held accountable.
My recommendation to law enforcement agencies: Realize that swatters are almost always going to place a call from outside of their target's locale. As such, they can't actually call 911 – they have to find a non-emergency number they can call that will escalate them to 911. These escalations should be red flagged as suspicious.
Trace the source of the phone call; if it traces back to a completely different state than the caller's claimed location, red flag!
If the source phone number of the caller isn't registered in their name (or anyone's name) then ask for proof of identification. If the caller refuses to identify themselves (my attacker hung up when asked) then it's a red flag!
I leave you with an excerpt from "The Crypto Anarchist Manifesto" (emphasis mine):
Image via Jameson Lopp
The leader in news and information on cryptocurrency, digital assets and the future of money, CoinDesk is a media outlet that strives for the highest journalistic standards and abides by a strict set of editorial policies. CoinDesk is an independent operating subsidiary of Digital Currency Group, which invests in cryptocurrencies and blockchain startups.