I Treated a Tax Foreclosure Like a DDoS Attack

Pulling off a pro se tax foreclosure defense in five days takes more than luck: it demands relentless focus, systems-level thinking, and the ability to write winning motions while the clock runs.

Feb 14, 2026

For Ann-Marie L., the brilliant, tough as nails lawyer who inspired me. Trevor O., the businessman expert who never stopped pushing me. And Kris B., who drove me around to gather evidence, submit filings, and serve people in my worst time of need.

At 4:35pm on February 13, 2026, I received a call from the NY State Supreme Court 8th District in Orleans County. My motion was granted. Then I vomited.
First time in my life. Not from fear, from release. My body had been running on pure adrenaline for five days and finally got the signal to stop.

In 2019, I defended a tier 1 streaming platform against an 80Gbps DDoS attack while a C-level executive stood behind me with a calculator, announcing our per-minute revenue loss in real time. I didn’t panic then, and I didn’t panic when I had five business days to stop the foreclosure of my house.

These events are related.

My mother died November 5, 2025. The property went into tax foreclosure. I didn’t receive notice, neither did she, because she was dead. Last month, I called the Orleans County Treasurer and learned the house was scheduled for auction on February 17.

Payment plan? Refused They were dead set on foreclosure sale. No lawyer would take my case on such short notice (or they suggested I file Ch11). I had ZERO legal training.

I’m a systems engineer. I’ve spent 20 years debugging distributed systems under pressure. So I treated this like any other incident.

The severity was critical: loss of primary residence. The root cause was improper service and notice under Real Property Tax Law Article 11. The timeline was a few short weeks to auction. The stakeholder was me, vs. the NYS Supreme Court & Orleans County.

I spent the first two days doing research. I downloaded every granted Order to Show Cause motion I could find from NY courts. I read Real Property Tax Law Article 11 like I was reading RFC documentation. I looked for the pattern.

The pattern was clear: Courts grant emergency relief when there’s a procedural defect, when the movant can cure the underlying debt, and when irreparable harm is imminent. I had all three.

The procedural defect was obvious: improper notice. My mother was dead. I never received service. That’s a constitutional due process violation. If they can’t prove they served notice correctly, the entire foreclosure is void. The ability to cure was documented: I’m the beneficiary of my mother’s life insurance through the New York State Teachers’ Retirement System. $15,721.77, enough to cover the redemption amount (with a couple extra thousand bucks out of my pocket) . The irreparable harm was simple: They were selling my house in five days.

On day three, I gathered evidence. Death certificate. NYSTRS beneficiary letter showing the $15,721.77 incoming. Proof of residence. I documented everything like I was building a post-mortem for a production outage. I needed to show standing as the heir, prove the defect in notice, demonstrate ability to pay with the NYSTRS documentation, and establish immediate harm from the scheduled sale date. Every claim needed evidence. No evidence, no credibility.

Day four was build day. I wrote the Order to Show Cause by reverse-engineering successful ones. Legal writing is just pattern matching. The format is caption with case identifier and index number, relief requested telling the court what you want them to order, grounds explaining why you’re entitled to it, evidence in the form of exhibits proving your claims, and a proposed order pre-written so the judge just signs it. I wrote it the same way I write runbooks.

The Order to Show Cause requested that the court stay the foreclosure sale to stop the bleeding, vacate any judgment entered without proper notice to fix the root cause, grant me redemption rights as permanent remediation, and require the county to prove they served notice correctly to shift the burden of proof back to them.

I kept the language clean and procedural. No emotional appeals. Just: here’s the defect, here’s the statute, here’s the evidence, here’s the relief.

The supporting affidavit was sixteen numbered paragraphs. Each paragraph established one fact. Who I am as heir and successor in interest. What happened when my mother died and no notice was received. What I have in NYSTRS funds to pay the debt. What I’ll lose if this proceeds? My primary residence. What the county loses if they wait, which is nothing since they get paid either way.

I attached two exhibits. Exhibit A was the death certificate. Exhibit B was the NYSTRS beneficiary documentation. No guessing. No assumptions. Just evidence.

On day five, I filed at 9am at the Orleans County Supreme Court clerk’s office. The clerk looked at my paperwork, looked at me, and asked if I was an attorney. :’)

“No. Pro se.”

She processed it. I walked out. Then I waited.

At 4:35pm, the court clerk called.

“Mr. Al-Khazaali, your Order to Show Cause has been signed by the judge. The sale is stayed. You’ll receive the signed order and a hearing date. Come tuesday, pick up the injunction to serve the the county treasurer & attorney.”

I thanked her. Hung up. Walked to my kitchen. And vomited.

The DDoS attack and the foreclosure required identical skills, just applied to different systems.

Threat assessment in a DDoS scenario means identifying the attack vector and determining scope. In a foreclosure, it means identifying the procedural defect and determining your timeline. Pattern recognition during a DDoS involves analyzing traffic signatures and known attack methods. In foreclosure, it’s studying legal precedent and successful motion formats. Resource allocation under a DDoS means routing traffic, spinning up infrastructure, implementing rate limiting. For foreclosure, it’s gathering evidence, citing statutes, building documentation.

Stakeholder management during a DDoS attack means dealing with C-suite executives holding revenue calculators and customer support fielding angry complaints. During a foreclosure, it’s understanding that you’re dealing with a judge under docket pressure and a county looking to move inventory off their books. Execution under fire when your site is bleeding revenue from a DDoS is the same psychological skill as filing a motion while the sale date approaches and you’re about to lose your house.

The domain changed. The methodology didn’t.

In both cases, panic is a choice. Systems fail predictably. Solutions exist if you can stay calm enough to find them.

I’m not special. I’m not a genius. I didn’t “teach myself law in five days.”

I stayed calm and read the documentation.

Legal systems aren’t magic. They’re systems. They have inputs, outputs, rules, and failure modes. If you can debug a distributed system, you can probably navigate a bureaucratic one.

The difference between me and most people facing foreclosure isn’t intelligence. It’s prior exposure to high-stakes technical problem-solving under time pressure. I’ve done this before, just in a different context.

Most people panic because they’ve never had to operate like this. I didn’t panic because I’ve defended production systems while executives calculated losses in real time. Compared to that, a county court clerk is just another stakeholder.

The DDoS attack didn’t teach me about foreclosure. It taught me how to function when the stakes are existential and the clock is running. That skill transfers.

I now have ninety days to pay the redemption amount. The NYSTRS check will clear. I’ll pay the county their money, taxes, interest, penalties, fees, all of it. They get made whole. I keep my house. The system moves on.

The county wasn’t evil. They were just running their process. Tax foreclosure is automated. Properties go delinquent, notices get sent allegedly, sales get scheduled. It’s a pipeline. Most people don’t have the resources or knowledge to interrupt it.

The law isn’t impenetrable. It’s just a protocol most people never have reason to learn. And if you’ve ever had to learn a new system under existential pressure, whether it’s a database migration, a security breach, or a crashed production environment, you already have the skill set to do this.

You just have to recognize that the same methodology applies.

Now if you’ll excuse me, I have actual infrastructure to maintain.

Aiman Al-Khazaali is a systems engineer who has never practiced law and doesn’t plan to start. He lives in Holley, New York, where he maintains distributed systems and occasionally defends his house from the local government.

Discussion about this post

Ready for more?