Hazmat called in California after a family finds human feces inside an Amazon package on their property

If you’ve ever had a package dropped at your front door, you already know the rhythm of modern life: a box, a label, maybe an Amazon tote, and a quick check to make sure it’s actually yours. Most of the time, it’s boring in the best way.

But in a KCRA 3 report, Denzen Cortez told a story out of Lincoln, California, that turns that whole routine inside out – because one family says an Amazon delivery left on their property wasn’t a normal package at all. They opened it and found what appeared to be human feces inside.

It’s the kind of headline that sounds like a prank until you remember something important: anything involving human waste is automatically a health issue, not just a gross-out moment. And in Cortez’s telling, that’s exactly why this situation escalated fast – quickly enough that hazmat crews were eventually involved.

According to Cortez, it’s a story KCRA said viewers would “want to hear,” and the anchor set the tone with a warning: if you think package deliveries are always the usual boxes and Prime stickers, think again.

That’s not just a dramatic intro. It’s a sign of where the story goes.

A “Delivery” That Wasn’t Ordered And Didn’t Make Sense

Cortez reported that Paige – identified as a member of the Lincoln family – was the one who first walked through what happened and what she saw.

The delivery wasn’t something they ordered, she said. And it wasn’t just misplaced, delayed, or mis-scanned the way people usually complain about packages.

Paige’s first confusion, according to Cortez, was the container itself. She described it as a bright neon tote, and at first she wondered if it was something like a construction tote or equipment – something that might make sense in a rural or semi-rural area where people are always hauling tools and supplies.

That detail matters because it explains why the family approached it like a normal delivery at first. It looked like a legitimate shipping tote, not a random trash bag tossed in the yard.

But the moment Paige opened it, the story changed.

Cortez quoted Paige saying that once it was opened, it was clear what it was: “human feces” with napkins inside – the kind of brown, drive-through napkins you’d recognize immediately.

In other words, it didn’t look like spilled food. It didn’t look like some weird package stuffing. It looked like someone used the tote as a waste container and left it there.

And that’s why this goes beyond being “gross.” It becomes a contamination question, and the family’s reaction starts to make a lot more sense.

Where The Tote Was Found And Why That Raises Even More Questions

Cortez said the family found the tote tucked behind branches and bushes on their property.

Paige described it as being placed in a way that looked sneaky, like someone tried to hide it while still leaving it on their land.

That detail is unsettling because it suggests the tote wasn’t dropped accidentally in plain sight. It wasn’t a simple “wrong house” delivery that got left on the porch. It was, at minimum, left in a spot that made it harder to notice right away.

And once you start thinking about intent, you start thinking about risk.

Because if someone intentionally hid a tote containing human waste on private property, you’re not dealing with a normal delivery error. You’re dealing with behavior that crosses into something else – reckless at best, criminal at worst, and definitely not something a family should have to troubleshoot like a customer service complaint.

Even without jumping to conclusions, it’s easy to see why Paige and her family didn’t just shrug and throw it away.

You don’t “take care of it” yourself when it involves bodily waste from an unknown person. You treat it like a biohazard until proven otherwise.

The Phone Call To Amazon And Why Paige Pushed Back

One of the most telling parts of Cortez’s report is how Paige described the family’s first contact with Amazon.

Paige said Amazon initially told her something like, “We’ll send someone to pick it out.”

Her response, in Cortez’s telling, was immediate and blunt: you can’t just send a driver to pick this up. She called that idea “horrid.”

That reaction is completely reasonable.

Delivery drivers are not trained hazmat workers. They’re not equipped to handle biohazard material, and they shouldn’t be put in that position. If companies treat something like this as just another “oops, wrong tote,” they’re not only risking customer health, they’re risking worker safety too.

Cortez’s report makes it sound like Paige wasn’t just angry – she was alarmed by the casualness of the initial response.

And honestly, that’s the part that sticks with you.

A lot of customer service systems are designed to handle missing packages, damaged items, wrong orders, and refunds. They are not designed to handle “someone left human feces in a delivery tote on my property.”

When something falls outside the script, you find out whether a company can adapt quickly, or whether it tries to push a bizarre incident through the same pipeline as a normal complaint.

In Paige’s case, Cortez suggests she had to forcefully make the point: this isn’t a simple pickup request.

Hazmat Response And The “Contamination” Fear

Cortez reported that Amazon ultimately sent hazmat crews to retrieve the package from the family’s residence.

That alone tells you how serious it became once the situation was understood.

Paige also explained what bothered her most. In Cortez’s story, she said she was disturbed by the idea of contamination – what that means for other packages, and what it means if a tote like this moved through normal delivery channels.

She put it in a very human way: what are they touching that we’re touching?

That question is the real heart of the story, because it’s not just about one gross tote. It’s about trust.

The entire delivery economy runs on trust that packages are handled normally, that containers aren’t contaminated, and that mistakes are mostly harmless.

When something like this happens, it doesn’t just disgust people. It rattles the idea that the system is clean and controlled.

Even if this turns out to be a one-off incident, the fear is easy to understand: if a delivery tote can contain something like that, and still end up on someone’s property, what failed along the way?

And who else might have been exposed before Paige even opened it?

This is also where the hazmat response makes sense. Hazmat isn’t just about cleanup. It’s about containment and preventing exposure, especially when you can’t verify the source of the waste or whether anything else was contaminated.

The Mystery Of How It Happened

Cortez noted that Paige and the family didn’t order the tote, and he emphasized the “mystery” angle of the story.

That mystery matters because there are multiple possibilities, and each one points to a different kind of problem.

If it was an intentional act by someone – whether a trespasser, a prankster, or someone angry – that raises safety concerns for the family and potentially for neighbors.

If it was connected to a delivery worker or a mix-up in the delivery process, that raises concerns about workplace conditions, oversight, and how Amazon handles unusual incidents.

If it was a third party using an Amazon tote for some unrelated purpose and then dumping it, that raises concerns about how these totes circulate, who has access to them, and how easily they can be misused.

The report doesn’t claim to know which explanation is true. It simply presents what the family found, how they reacted, and what Amazon did afterward.

But it’s hard not to notice that every potential explanation still ends with the same conclusion: a family should not have to deal with this.

Amazon’s Internal Investigation And The Lack Of Comment

Cortez said the family shared an email with KCRA in which Amazon stated an internal investigation is underway into the delivery.

That’s a key point, because it suggests Amazon is treating it as a serious incident rather than a simple customer dispute.

Cortez also reported that KCRA reached out to Amazon for comment and did not hear back.

That silence doesn’t prove anything by itself, but it does leave the public with unanswered questions – especially since this is the kind of story that spreads fast and makes people wonder whether something similar could happen to them.

The longer the company doesn’t publicly explain what happened or how they’re preventing repeats, the more the story becomes a stand-in for bigger anxieties about modern delivery systems: the scale, the speed, the automation, and the way accountability can feel foggy when something goes wrong.

The Part That Feels Bigger Than One Gross Tote

Here’s the uncomfortable truth: stories like this stick because they tap into a sense that everyday systems are becoming less personal and harder to control.

When a delivery goes wrong, you’re not talking to a person who knows your neighborhood. You’re talking to a huge machine – apps, call centers, scripts, and policies.

Most of the time, that machine works well enough.

But when it fails in a bizarre way, like the incident Cortez described, people don’t just get mad. They feel exposed.

And Paige’s reaction in the KCRA story captured that feeling: the worry isn’t only the tote sitting on her property. It’s the idea that this could touch other packages, other homes, other hands.

If you strip away the shock value, the story becomes a question about standards.

How are delivery totes tracked and controlled?

How does a company handle a biohazard report?

What protections exist for customers and for drivers?

And how quickly does the system shift gears when the situation is outside the normal playbook?

Cortez’s reporting doesn’t pretend to have all those answers. It just shows what happened to one family, how quickly it escalated, and how strange it felt to live through.

And maybe that’s why it lands so hard. Because for the family in Lincoln, this wasn’t a viral joke or a weird headline. It was their property, their safety, and a delivery they never asked for—one they’ll probably never forget.