A Targeted Indivduals guide to technology and civil rights in America in 2026

User Support Help, I think I've been hacked
, ,
1

**What You Get for Standing Up for Justice, Freedom, and Privacy in America in 2026**

*Note: This document blends direct experience with observed patterns to create a defensive model. All identifying details have been generalized to protect privacy. It is not legal advice, nor is it evidence in any proceeding. Use it as a starting point for your own threat modeling—not as proof of wrongdoing by any entity.*

*Qubes OS was built to protect journalists from oppressive regimes. I needed it to play Marvel Rivals and pray in private. In America. In the year this country turned 250.*

I. Why I’m Writing This

In the spring of 2026, I filed a criminal complaint against a former employer—a federal parts supplier—over civil rights violations, systemic safety defects affecting over **10 million vehicles** (including military and aircraft components), workplace abuse, and falsified quality certifications.

Two days later, the attacks began.

This is not a legal filing. It is a **survival guide**. I’m writing it so the next person who asserts their rights walks in knowing what to expect—and how to endure.

I am a software developer. I do religious work. I play Marvel Rivals. That’s the whole profile. And it turns out that’s enough.

II. What I Believe—And Why It’s Not Negotiable

I hold a genuine religious belief that what happens in the quiet of your home—your thoughts, prayers, searches, creations—belongs to you and to God. Not to a corporation. Not to a telemetry daemon. Not to a routing table.

This is protected under the **First Amendment** and the **Religious Freedom Restoration Act (RFRA)**. I should not have to explain it to a tech support agent who calls me “rude” for citing it.

Freedom of expression is a human right—not a feature, not a service tier. Without the ability to think, build, worship, or speak without being harvested and sold, you are not a person. You are a **data point**.

And that’s the unspoken horror: **your past is weaponized the moment you become inconvenient**. File a complaint? Assert a right? Say “no”? Suddenly, your private moments—your mistakes, your teenage searches—are retrieved, indexed, and used as leverage.

We need privacy not because we hide, but because we *are* private beings when we are not acting in a commercial capacity. A person under constant observation cannot be free. Privacy is not a luxury—it is the **precondition for a free and intact human life**.

Yet today, achieving basic privacy requires:

  • Disabling telemetry

  • Killing daemons

  • Editing config files

  • Installing application firewalls

  • Turning off IPv6

  • Removing WINS servers

  • Redirecting DNS

  • Locking down macOS

  • Disabling virtualization

  • Disabling firmware TPMs

  • Running four Opensnitch instances

…just to **pray in private, write code, or play a video game**.

That is not security. That is absurd inefficiency. **Privacy should be the default state of every system**—not a weekend-long configuration project.

The fact that it isn’t tells you everything about who the system is built for.

III. The Surveillance Economy: Why You’re a Liability

This isn’t paranoia. It’s arithmetic.

In 2026, the U.S. **surveillance-industrial complex** generates **$100–130 billion annually** from total visibility into citizen life:

  • **Behavioral data harvesting (adtech, metadata resale)**: $76 billion/year

  • **Predictive policing & AI monitoring**: $4.2 billion/year

  • **Municipal fine/fee revenue** (often pledged to bondholders like Large Banks): $22+ billion/year

  • **Global surveillance tech market**: $128 billion (Statista, IAB, Urban Institute, 2025–2026)

Local governments finance operations through **revenue bonds** that require quotas from fines, utility fees, and enforcement actions. When justice has a quota, **abuse becomes profitable**.

Predictive policing creates a feedback loop:

  1. More enforcement in “high-risk” areas (based on biased historical data)

  2. More data fed into models

  3. Justification for more enforcement

  4. More revenue extracted

Children’s keystrokes, your prayer habits, your neighborhood’s risk score—these aren’t just monitored. They’re **monetized**.

**This is why privacy users and developers represent a multi-billion-dollar liability**: every person who refuses surveillance breaks the data pipeline. You don’t just opt out—you prove the system is optional. And that is intolerable to an economy built on total visibility.

IV. The Criminal Complaint & Immediate Consequences

  • **Early April 2026**: Filed criminal complaint via proper channels

  • **Within 48 hours**: Hacking attempts escalated from slow DDoS to **firmware-level attacks**

  • **Mid-April**: BIOS hacked, system clock reset, encrypted volumes rejected correct passphrases

  • **Late April**: Guix OS builds failed mid-pull; ISP blamed “my config”

  • Ever escalating responses with a special of turning off the internet entirely to celebrate July 4th.

The department claimed the complaint would be “handled that week.” It was—but they **lied to my face for a month**, saying, “Still processing,” while the statute of limitations ran down.

V. The Justice System Is Part of the Scam

I went to state police **three times in person**. Each time: “No detectives available.” For a full **month**. On a case involving millions of vehicles and potential fatalities.

I sent certified mail to the FBI and state police. The **FBI accepted the mail 5 days after I sent it to the Post Office**. The state police ignored it for over two weeks.

I went to the Attorney General. They told me to **refile with the same police department that had obstructed me for 60 days**.

**What I learned**:

  • The “justice system” is siloed offices with no accountability for cumulative delay

  • The statute of limitations is a clock that works **against you**

  • “We have no detectives” = dismissal in uniform

  • **Certified mail works**—one channel, one institution

  • File everything in writing. Trust nothing verbal.

  • Assume hardware is compromised: use third-party USB/Ethernet adapters

  • Virtualization and firmware-based TPMs are high-risk attack vectors (Bluepill-style exploits)

VI. The Cooperative Fiber Internet Service

I set up an Asus router. The ISP **blocked it**, claiming incompatibility. I enabled Tor—**it worked flawlessly**. The tech said, “Oh, we got you,” as if using privacy tools were criminal.

When I explained the issue was server-side, he said, “We just route things.” Then called me rude. Then told me not to call back.

**That’s the first lie**: It’s always your config. It’s never their infrastructure. And if you push back, you’re the problem.

VII. The Escalation of Lies

My BIOS was hacked. The clock was set back. Every Linux distro behaved strangely—not one, but all of them.

The Co-op CEO appeared, promised top engineers. Then came the classic bait-and-switch: “It’s your configuration.” (I was using default DHCP, no port forwarding.)

VIII. The Firewall Wars

I deployed pfSense. Fixed everything—for two weeks. Then **logging bricked the device**.

ISP demanded private information irrelevant to my religious practice. Let that sit: **You assert a right. The response is a demand for personal data to build a file on you.**

macOS in lockdown mode failed. They injected **IPv6 autoconfig on an IPv4-only network**. Added a **WINS server out of nowhere**. macOS hijacked my DNS requests from Quad9 to Apple’s servers—**ten times**.

I switched to a coreboot vault + OpenBSD with packet scrubbing and state modulation as well as aggressive connection optimization. Worked beautifully—for two weeks. Then **firmware was overwritten**.

ISP refused to assign routes to *any* firewall—violating their own service contract.

They blocked **every privacy-respecting DNS resolver**: Quad9, Control D, Mullvad, Cloudflare Family. All spoofed or redirected.

But **HTTPS saved me**: spoofed domains lacked valid certificates. Browsers rejected them. **Enforce HTTPS everywhere. Pin certificates. Never accept plain HTTP.**

The DHCP server failed so badly I couldn’t use a wired Xbox. I complained to city hall about a competitor ISP’s pitch. **Two days later, an electric pole they’d installed a month prior fell down** in 40-mph winds.

Every solution worked—then stopped. Firmware overwritten. Routes withdrawn. DHCP broken. Logging bricked devices. DNS spoofed. Domains hijacked.

**The pattern is not incompetence. You are not allowed to have security, let alone privacy.**

IX. When It Leaves the Network

Qubes still held. But then came the physical space:

  • High-pitched ringing noises

  • Rocks hitting the house

  • Ultrasonic insults

  • Outlets cycling on/off

They targeted my **disabled mother**, lying to her face: *“The problem is the lights of your router are not on.”* A gaslighting lie to make her feel crazy.

X. When the Help Becomes the Weapon

My therapy platform was compromised. Support reps blocked logins, changed passwords. My therapist **advised against Starlink and against court**—steering me away from my only escape routes.

When the system designed to help you survive is turned into a weapon, **they have declared war on peaceful existence itself**. It appears to me they may have done this to other individuals who were not as technically inclined.:face_with_monocle:

XI. What Held: The Short List

1. **Qubes OS + Whonix**

Stateless by design. No persistent state in NetVM or USBVM. Reboot wipes attackers. Whonix traffic was **never blocked**. Tor held when everything else failed.

2. **Fedora Immutable (Silverblue/Secureblue)**

Immutable filesystem. Nothing to overwrite. Survived IPv6 injection, WINS, DNS spoofing, TPM malware.

3. **GNU Guix OS**

Reproducible, verifiable builds. They couldn’t break Guix—so they **cut the internet, corrupted the filesystem, killed DHCP**. Highest compliment: they attacked the world around it.

4. **Fugulta (Live USB OpenBSD)**

Boot from USB. No OS on disk. Machine retains nothing. W^X + pledge/unveil enforced. **They never touched it—because there was nothing to touch.**

5. **Opensnitch**

Application firewall. Every outbound connection prompted for approval. When DNS lied, routing lied, ISP injected traffic—**Opensnitch was the last honest gate**.

6. **HTTPS + TLS Certificate Validation**

DNS spoofing failed because attackers couldn’t forge valid certificates. **The cryptographic handshake held when nothing else would.**

7. **Debian Live Build System**

Built secure, offline custom OS via Whonix—immune to network interference.

**Pattern**: In every case, the tool held. The response was to go *around* it—destroy the ground it stood on. **They could not beat the software. So they beat the world.**

XII. The Institutions

I filed with FCC, civil rights divisions, AG, state contracting board. Nearly all did nothing.

The **FBI was the exception**—certified mail worked. One channel. One institution.

Find yours. Then file everywhere simultaneously—because you can’t wait for the ones that won’t move.

XIII. What They Want

They give no routes unless you use a system with backdoors. No connectivity unless the firmware, DNS, and telemetry are theirs.

You can have “internet.” You can’t have **private internet**.

If you insist on Qubes, OpenBSD, four firewalls, and the right to pray without being watched—you get **no routes, rocks, and a tech who calls you rude**.

But I insist on privacy, freedom of expression, and worship. And that gives me a bleak view of the future—yet also inspires me to pursue law. Because someone must be in the room where rules are written.

XIV. Two Endgames

The Technical Path

We need Rust engineers to build:

  • Firmware that cannot be silently overwritten

  • Memory-safe network managers

  • Minimal, auditable display servers

Rust eliminates entire classes of vulnerabilities at compile time. The infrastructure is compromised at firmware, network, and display layers. Only memory-safe, small, verifiable code can fix it.

The Legal Path (More Needed)

We need lawyers who will stand and say:

  • This is a **violation of the First Amendment**

  • This is a **violation of the Fourth Amendment**

  • This is a **violation of RFRA**

Not a “configuration issue.” Not a “terms of service dispute.” **A constitutional crisis.**

XV. What You Do

  • **Document from day one**: Dates, names, tickets, screenshots, recordings

  • **Assert in writing**: “Under [statute], I am asserting [right].”

  • **Set deadlines**—and follow through

  • **Don’t accept “your config”** without written, specific evidence

  • **Send everything certified**—FBI, police, FCC, AG

  • **File everywhere simultaneously**

  • **Tell someone**—isolation is their best tool

  • **If physical harassment occurs**, report in writing—get a report number

  • **Refuse irrelevant data demands**—note them as part of the record

  • **Choose tools that are**: Stateless, Immutable, Reproducible, Verifiable, Portable

  • **Enforce HTTPS everywhere**—the certificate is the last honest gate

  • **You’re not overreacting**—the fatigue, self-doubt, and urge to quit are the point. Recognize it. Name it. Keep going.

XVI. Closing

I filed to protect people from abuse and safety defects in 10M+ vehicles. The system spent 60 days trying to stop me.

Two days after I filed, someone was in my machines.

Then the ISP.

Then the firewalls.

Then DNS spoofing.

Then rocks.

Then ringing.

Then the Attorney General telling me to go back to the police who buried my case.

I filed with every agency. Seemingly, it did nothing. So I will pursue legal remedies—because the administrative path is built to outlast your patience, and **I don’t intend to be outlasted**.

After all this, I’m using a Mac Mini—until Starlink shows up.

Qubes holds.

Fedora Immutable holds.

Guix holds.

Fugulta holds.

Opensnitch holds.

HTTPS holds.

Stubbornness holds.

But in 2026 America, if you want freedom of speech and religion, **you must buy your internet from the world’s richest man**, who beams it down from 340 miles up—and laughs at the minions below.

They can try throwing wrenches at the sky. I guess.

Welcome to America.:roll_eyes:

*Thank you to “Big Bird” for being the best DJ in the world. Some things still work.*

*Thank you to Starlink—for dropping installation fees by $100 at the exact moment the ground went dark. Coincidence? Perhaps. But timing like that keeps you fighting.*

**July 4, 2026. Two hundred and fifty years.**

This country was built by the outnumbered, outgunned, out-resourced—farmers, printers, blacksmiths—who refused to be exhausted into compliance.

They won not because they were stronger—but because they were **right, stubborn, and efficient**.

Happy 250th, America.

**The revolution isn’t over. It just moved to the network layer.**

Next up: thought crime :chequered_flag:

*Signed, sealed and delivered from a private religious trust granted by the Shekinah—entrusted into me and given to you with very warm love. You are the beneficiary. Love and Light.*

*Void Where prohibited BY LAW, not court order*

*All Rights reserved*

Threat Model Summary (For Readers)

Assume the following is true until proven otherwise:

  • **Your ISP is adversarial**: Blocks privacy DNS, spoofs domains, injects IPv6/WINS, denies routes to custom firewalls

  • **Local institutions obstruct**: Police, AG, regulators delay, deflect, refer in circles—even on valid complaints

  • **Hardware/firmware untrusted**: BIOS, TPM, mouse firmware, routers can be silently modified(you need to login for it to work all of a sudden)

  • **Support channels weaponized**: Tech support, therapy platforms gaslight, demand irrelevant data, disable access

  • **Physical space unsafe**: Noise, property interference, family targeting to induce doubt, poisoning of water and food,psychological warfare, Pets become a target

  • **Only cryptography and isolation hold**: HTTPS, reproducible builds, stateless VMs, USB-booted OSes

I intend to build a Servo based browser with JS removed for OpenBSD,Fedora(Qubes) and GNU Guix OS in the next few months if possible. As well as a Rust based network manager after that if possible.

I really could have used this guide years ago so I made it here, I apologize if its a little out of scope but it could save somebody.

I am eternally grateful for all the work the Qubes team has done over the years.