The Weak Link This Week Wasn't Code. It Was Trust.

Key points

• Home streaming boxes and consumer routers were quietly enlisted into proxy networks that hide criminal traffic behind ordinary household IP addresses.
• Clean-looking open source projects pulled in tampered dependencies, meaning developers who did nothing obviously wrong still shipped malware.
• Password reset flows and single sign-on shortcuts were abused to take over accounts without ever cracking a password.
• AI assistants were tricked by hidden instructions buried in documents and web pages, a technique known as prompt injection.
• Fake proof-of-concept exploit code posted on developer sites installed malware on the researchers who ran it.

A streaming box should not need a threat model. Neither should a login screen, a demo repository, a password reset, or a browser pop-up asking for permission.

And yet, this week, every one of those ordinary things became the way in.

The pattern was not clever zero-days, meaning brand new software flaws nobody had seen before. It was misplaced trust. Systems assumed something was safe because it looked safe. Attackers noticed.

What actually happened this week?

Several separate stories, one shared weakness. Here is the plain version.

First, home devices. Researchers tracked criminal groups turning consumer gear (cheap Android TV boxes, older routers, smart plugs) into what security people call a proxy botnet. That is a network of hijacked household internet connections that criminals rent out to route their traffic. When a fraudster logs into your bank from what looks like a neighbour's home broadband, the bank's fraud checks tend to shrug and let it through. The device owner sees nothing wrong. The bandwidth cost is tiny. The trust the bank places in "residential" IP addresses is the whole point.

Second, the software supply chain. Developers pulled in open source packages that looked fine and had clean commit histories, but which quietly depended on other packages that had been tampered with. First reported in tracking by The Hacker News and others, the pattern keeps repeating: the top layer is trustworthy, the layer underneath is not, and nobody checks all the way down.

Third, identity. Attackers kept finding ways around passwords rather than through them. Weak password reset flows, single sign-on tokens that lived too long, help desks that reset multi-factor authentication (the second code you type after your password) for anyone who sounded stressed enough on the phone. No password was cracked. None needed to be.

Fourth, AI. Assistants that read documents, browse the web, or summarise emails on your behalf were tricked by instructions hidden inside the very content they were reading. This is called prompt injection. A malicious web page tells the assistant, in text the user never sees, to send private data somewhere. The assistant, trained to be helpful, obliges.

Why does this keep happening?

Because trust is cheap to grant and expensive to verify.

A bank trusts residential IPs because checking every login properly is slow. A developer trusts a popular package because reading every line of every dependency is impossible. A help desk trusts a caller because being unhelpful gets complaints. An AI trusts the text in front of it because that is what it was built to do.

Each shortcut is reasonable on its own. Stacked together, they are the attack surface.

What should ordinary people do?

A few practical things, none of them dramatic.

If you own a cheap streaming box or a router more than five years old, check whether the maker still issues updates. If not, replace it when you can. Turn off features you do not use, especially remote access.

On accounts that matter (email, banking, work), use a password manager and turn on multi-factor authentication using an app rather than SMS. If a service offers passkeys, use them.

Be wary of AI tools that browse the web or read your inbox on your behalf. They are useful. They are also gullible. Do not give them access to anything you would not hand a stranger.

The common thread this week was not sophistication. It was assumption. Every layer assumed the layer next to it had done the checking. None had.