Let’s get something straight:

The line between biology and technology isn’t blurry anymore. It’s gone.

Your body isn’t just like a computer—it functions like one, is treated like one, and in many ways, is more vulnerable than one.

And if you’ve ever felt like you were being influenced, tracked, nudged, or optimized without really understanding how—it’s because you are. Your biology has already been converted into code. And that code is being analyzed, targeted, and in some cases, exploited.

By design.

So the real question isn’t if your body can be hacked.
It’s how—and where—it already has been.

Let’s start by breaking down the stack.

What If Your Body Runs on Code—and the Code Is Already Public?

You’ve probably heard it before: “Your body is like a computer.”

But what if we stop treating that like a metaphor—and start treating it like an attack surface?

Because if you look under the hood of modern bio-cybersecurity research, here’s what you’ll find:
Your biology is being modeled, mapped, and manipulated using the exact frameworks we use to secure digital systems.

This isn’t a thought experiment. This is already how your genome gets stored. How biotech software compiles protein expressions. How hackers test exploits.

Let’s reframe the human system using the language of cybersecurity:

Still think this is just a fun analogy?

In 2017, a team at the University of Washington encoded actual malware into synthetic DNA. When sequenced by a computer, the code executed—and took control of the machine. That wasn’t sci-fi. That was a proof of concept. And it worked.

So no—this isn’t just philosophy.
This is how your data gets turned into profit.
This is how your behavior gets profiled.
And this is how attackers get root access to your biological operating system.

You are no longer just the user.
You are the infrastructure.

And every single system in your body—neurological, emotional, chemical, metabolic—is now a potential exploit vector.

Where Are the Backdoors in Your Body?

Let’s stop asking if someone might hack your biology—and start asking how they already are.

Because the truth is, we didn’t get breached through some dramatic cyberwar moment.
We got breached by signing terms and conditions we didn’t read.

These are beyond hypothetical threats. These are already happening—and they don’t require a hoodie or a zero-day. They just need you to click “I agree.”

Let’s map out what that actually looks like:

And here’s the worst part: none of this required someone to "hack" you in the traditional sense.
No malware. No exploits. No brute-force attack.

It happened because we volunteered.
We handed over the source code.
We plugged in the devices.
We trained the algorithms on our own behavior.

That’s the modern threat model.

So if you’re still thinking cybersecurity is something that happens to your laptop—you’re missing the bigger picture.

The network includes you now.

And you’re already online.

What Happens When Your Source Code Gets Dumped?

You know what happens when someone leaks a password?
You change it.

You know what happens when someone leaks your DNA?
You can’t.

There is no reset button for your genome.

So when 23andMe got breached in 2023—exposing nearly 7 million users’ genetic profiles, ethnicity markers, and health data—that was already a catastrophic privacy failure. But what came next made it even worse:

The company filed for bankruptcy.

And that’s when the real nightmare starts.

Because here’s what most people don’t realize: in bankruptcy court, everything a company owns gets reassessed as an asset. Not just the desks, the trademarks, or the office leases. The data. Especially the data.

That includes entire databases of genetic information—the raw DNA files, the ancestry maps, the health risk profiles, even the behavioral markers embedded in their algorithms. It all gets wrapped into what lawyers call “intellectual property” or “consumer data assets.” And those assets?

They’re up for sale.
To the highest bidder.
With zero obligation to inform you or get your consent.

Let that sink in.

Your genetic code—arguably the most intimate, permanent form of personal information that exists—can be auctioned off like leftover furniture. Sold to private equity firms, research conglomerates, data brokers, even international buyers. Once that transaction happens, you lose all control.

You don’t get notified.
You don’t get a say.
And you sure as hell don’t get a rollback.

This is the legal system doing exactly what it was designed to do: liquidate assets to pay off debt. And your DNA? That’s one of the most valuable assets on the table.

And here’s the worst-case scenario—the one we never talk about enough:

• A buyer scoops up that database and starts building predictive health models—flagging users as high-risk for chronic illness, addiction, or cognitive decline.

• That data quietly makes its way to insurers, employers, or financial firms, who use it to shape risk scores, deny coverage, or adjust premiums—without ever telling you why.

• Someone cross-references your genome with public genealogy records and links you to a relative under investigation. Suddenly, you’re in a law enforcement database through no action of your own.

• A foreign entity or surveillance contractor acquires access to a dataset containing markers for mental illness, aggression, or susceptibility to addiction—and uses it to train targeting algorithms.

• A biotech firm uses your raw data to develop a drug, patents the outcome, and profits off your genome—with no compensation, recognition, or control on your end.

And let’s be clear: this is already happening in fragments. What bankruptcy does is open the floodgates and remove the last layers of protection.

This is why it’s not enough to secure genetic data when a company is solvent. We need laws that travel with the data, even after a company collapses. Because if your DNA is treated like inventory, your body becomes a product line.

DNA = Zero-Day Forever

In software, a zero-day is a flaw no one knows about until it's exploited.
In bio-cybersecurity, your genome is a pre-installed zero-day.

Once it’s digitized—by a lab, a health app, a fun little ancestry service—it becomes:

• A permanent identifier that tracks you across systems

• A predictive blueprint for everything from health risks to personality traits

• A shared fingerprint that exposes your family tree, even if they never consented

• A commodified asset traded between researchers, insurers, and advertisers

And in the wrong hands? A targeting vector for biological blackmail, discrimination, or worse

Think data anonymization protects you? It doesn’t.

Researchers have already shown that most DNA can be re-identified by combining genetic markers with public genealogy records and a bit of metadata. Even if your name is stripped, your genome still acts like a GPS tracker pointing back to you—and your relatives.

This is why deleting your genetic data isn’t optional—it’s urgent.

And Then There’s Weaponized DNA

Yes, this actually happened.

In 2017, researchers at the University of Washington embedded malicious code into a strand of synthetic DNA. When that DNA was sequenced, the code executed on the lab computer and took control of the system.

Read that again.

DNA carried malware. The computer read it. And got pwned.

That’s the digital-bio crossover nightmare in full color:
Genetic material as an exploit payload.
Your bloodline as a backdoor.

Now scale that out.

Imagine a bad actor poisons a genomic dataset. Or smuggles tainted DNA into a research pipeline.
What happens when those sequences are used to train AI models, build pharmaceuticals, or diagnose patients?

You’ve now got weaponized biology running on cloud-connected infrastructure—and most of those systems aren’t air-gapped or secured.

So yeah, your genome is a target. Not just for hackers. For adversaries. For surveillance states. For data brokers and biotech firms who see your body as an unclaimed asset.

This is why DNA can’t be treated like cute ancestry data anymore.

It’s code.
It’s dangerous.
And once it leaks—it’s everyone’s problem.

When Corporations Start Writing Code for Your Body

Let’s talk about Ozempic.

Originally developed as a diabetes drug, it became a runaway success because of what it really did: suppress appetite by manipulating GLP-1 receptors in the brain. Millions started using it. People ate less, craved less, and in some cases, transformed their entire relationship with food.

But this story is about countermeasures, not health.

Because while Ozempic was quietly patching a glitch in the metabolic loop, Big Food was watching something far more alarming:

Declining snack sales. Shifting purchasing patterns. Consumer behavior changing—not through marketing, but through chemistry.

And they responded exactly how you’d expect a threatened industry to respond:
They engineered new inputs designed to override the patch.

We’re talking about reformulated flavors, aggressive additives, new compound profiles built in labs—not for taste, but for neurochemical exploitation.

These aren’t food products. These are exploit payloads—scripts written to bypass your satiety response and reboot craving cycles that Ozempic tried to suppress.

You install a hunger-suppressing patch.
They install an override.

Welcome to the arms race.

This is literal code warfare at the biochemical level—your neurobiology caught in the crossfire between pharmaceutical companies and corporate food giants.

Let’s be clear: this is not about “junk food is bad.” That’s too simplistic. This is deliberate engineering of inputs to hijack your internal processes. We’re in the middle of a feedback loop between:

• Corporations who profit from overconsumption

• Pharmaceuticals that attempt to patch the damage

• And consumers trapped in the middle, having their physiology rewritten by forces they can’t see

Biology becomes a software platform. Your appetite, mood, and focus become interfaces for external code. And like any platform, the one who controls the update cycle, the override scripts, and the default settings—wins.

This is not nutrition anymore.
This is system-level access.
And your body is running code written by someone else.

How to Build a Firewall Around Your Flesh

You can’t opt out of being biological.

But you can stop being an easy read.

If your body is a system—and it is—then it needs what every vulnerable system needs: a firewall. Something to define what gets in, what runs, and what gets shut down on sight.

This isn’t an app. It’s not a product. It’s a posture—a mindset built around layered defense. A refusal to let your code be open-source to anyone with a login screen or a marketing budget.

Here’s how you start locking down the stack.

Layer 1: Secure the Source Code (DNA)

Your genome is not a party trick. It’s not a parlor game. And it sure as hell isn’t a freebie for data-hungry startups wrapped in “ancestry curiosity.”

If you’ve sent spit to a company like 23andMe, you’ve already uploaded your biological root directory to the cloud. That data is now floating in datasets sold to researchers, shared with insurers, and stored in cloud servers that, as we’ve seen, do get breached.

Want to start protecting your source code?

• Stop submitting your DNA unless you understand exactly what’s being done with it

• Request deletion from any service you’ve used—yes, even if they say it’s “anonymized”

• Use burner emails and aliases for health tech and wearable platforms

• Never connect your fitness tracker or menstrual app to anything that stores identifiable data

DNA is permanent. It can’t be revoked. Once it's out, it’s not just your exposure—it’s a key to your relatives' data too.

Treat it like the most sensitive credential you’ll ever have. Because it is.

How to Delete Your Genetic Data—Right Now

If you’ve used 23andMe, Ancestry, MyHeritage, or any other DNA testing service, your data is likely still stored in their systems—and possibly shared with partners. Deleting it won't undo what’s already been leaked, but it will stop future exposure.

Here’s how to lock it down:

1. Log into your account on the service’s website.

2. Find the data or privacy settings—usually under "Account Settings" or "Data Management."

3. Request deletion of:

   • Your raw DNA data

   • All analysis reports

   • Your physical DNA sample (if stored)

4. Submit a written request to customer support confirming you want full deletion. Be specific.

5. Use GDPR or CCPA (if applicable) to legally compel deletion. You don’t need to be in the EU or California—just say you're exercising your rights under data protection law.

6. Request written confirmation that your data and sample have been removed from all systems, including backups.

Bonus: Use a burner email and alias for any future health-related apps or wearables. Don’t ever tie your real name to your biology if you don’t have to.

Layer 2: Harden the Operating System (Cognition)

Your nervous system is an open API. Every ping—every ad, alert, headline, and notification—is a line of code trying to execute.

Start defending like it matters:

• Curate your inputs. That means browser extensions like uBlock Origin, Greyscale mode, and news feed blockers

• Keep logs. Track what changed your mood. What triggered your scrolling. What made you react

• Watch the install pipeline. What apps are running scripts in the background? What notifications are pulling you into loops?

• Train your algorithm on purpose. You do have the power to shape your feed to support your dream life. Every click is a vote. I dive deeper into this reprogramming strategy in another article.

• Use mindfulness as a circuit breaker. It’s not fluff—it’s a literal pause() function between stimulus and execution

Emotions are not soft. They are executable code running across every system—hormonal, behavioral, neurological.

If you don’t audit them, someone else will.

Layer 3: Control Third-Party Code (Food and Pharma)

Everything you consume is software. Not metaphorically—biochemically. And like all software, inputs can be clean, bloated, or malicious.

Start asking:

• Who wrote this code?

• What system is it designed to influence?

• Is this a patch or a payload?

Most of the supermarket isn’t food. It’s behavioral engineering—designed by labs, focus groups, and neurochemists with one goal: drive consumption loops that feel like choice but run like addiction.

You don’t need to be a biohacker. You just need to stop letting PepsiCo write your firmware updates.

Layer 4: Obfuscate Your Identity Perimeter

You’re not just leaking data. You’re leaking patterns.
And the systems reading those patterns are getting smarter, faster, and harder to spot.

They’re profiling:

• Your eye movement

• Your walking cadence

• Your typing rhythm

• Your emotional tone on Zoom calls

• Your listening habits on Spotify

This is not surveillance in the old sense. This is profiling at the behavioral layer—used to build models that know you better than you know yourself.

Disrupt it:

• Use multiple emails. Rotate usernames.

• Break your digital routines. Vary your behaviors.

• Cover your cameras. Obfuscate your browser fingerprint.

• Default to unpredictability—not invisibility.

The goal isn’t to disappear. It’s to become unreadable.

Layer 5: Lock Down the Digital Ports

Biological privacy and digital privacy are no longer separate concerns. Your smart watch is a backdoor. Your mental wellness app is an exfiltration tool. Your sleep tracker may as well be wiretapping your circadian rhythm.

Here’s what lockdown looks like:

• Use Signal, not SMS

• Use ProtonMail, not Gmail

• Use Firefox with hardened privacy, not Chrome

• If you’re ready: install GrapheneOS. Yes, it’s that serious.

And remember: every time you choose convenience over control, you widen your own attack surface.

If you wouldn’t leave SSH open to the world on a production server, don’t give your calendar app read access to your inbox.

Reduce exposure. Close the ports.

This is your perimeter. And it’s yours to define.

You Are the Infrastructure—Act Like It

This isn’t about protecting your data.

This is about protecting your system.

Because the moment you handed over your DNA, your attention span, your sleep cycles, and your biometrics to a dozen connected platforms? You stopped being just a user.

You became the infrastructure.

Every decision you make—what you eat, what you click, what you share, what you allow—writes to that infrastructure. You’re not outside the system looking in. You are the system being read, modeled, and modified in real time.

And if you’re not managing that architecture, someone else will.

That means thinking like a sysadmin. Not paranoid. Just aware.

• Who has access to you?

• What’s running on startup?

• Where are you leaking signal—through your habits, your apps, your language?

• What behavior patterns are so consistent they’ve become exploitable?

This is the real shift. It’s not about unplugging. It’s not about going analog.
It’s about becoming unreadable. Unpredictable. Unprofitable.

It’s about knowing where your logic is being outsourced—and reclaiming it.

Treat your routines like scripts. Your triggers like inputs. Your decisions like code.
Change what runs by default.

Log everything.

Patch constantly.

Run clean.

You don’t need to vanish.
You just need to stop being legible.

Because once you understand that every part of you—your biology, your emotions, your metadata—is being read like a system…

You stop being a target.

You become the architect.

Stay Curious,

Addie LaMarr

P.S. Love getting really deep into topics and sorting through all the details? I've put together a 48-page research report that goes super in-depth into how tech intersects with our biology—it's all cited and sourced for you to geek out on!