惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V2EX - 技术
V2EX - 技术
L
LangChain Blog
IT之家
IT之家
S
SegmentFault 最新的问题
博客园 - 三生石上(FineUI控件)
H
Hackread – Cybersecurity News, Data Breaches, AI and More
T
The Blog of Author Tim Ferriss
Blog — PlanetScale
Blog — PlanetScale
N
Netflix TechBlog - Medium
U
Unit 42
B
Blog RSS Feed
GbyAI
GbyAI
Microsoft Security Blog
Microsoft Security Blog
博客园 - 司徒正美
Apple Machine Learning Research
Apple Machine Learning Research
T
Threatpost
C
CERT Recently Published Vulnerability Notes
Cisco Talos Blog
Cisco Talos Blog
The Register - Security
The Register - Security
Vercel News
Vercel News
S
Schneier on Security
Spread Privacy
Spread Privacy
C
Cyber Attacks, Cyber Crime and Cyber Security
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
博客园 - 叶小钗
雷峰网
雷峰网
博客园_首页
人人都是产品经理
人人都是产品经理
P
Palo Alto Networks Blog
The Hacker News
The Hacker News
T
Tor Project blog
L
Lohrmann on Cybersecurity
Know Your Adversary
Know Your Adversary
D
Darknet – Hacking Tools, Hacker News & Cyber Security
C
Cybersecurity and Infrastructure Security Agency CISA
P
Privacy International News Feed
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
T
Tenable Blog
V
Vulnerabilities – Threatpost
大猫的无限游戏
大猫的无限游戏
博客园 - 【当耐特】
V
V2EX
Security Latest
Security Latest
A
About on SuperTechFans
Cloudbric
Cloudbric
S
Security Affairs
MongoDB | Blog
MongoDB | Blog
Y
Y Combinator Blog
Martin Fowler
Martin Fowler
TaoSecurity Blog
TaoSecurity Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
The 2026 Wireless Threat Nobody Prepared For: UWB Hacking, Relay Attacks, and Proximity Crimes
v. Splicer · 2026-06-12 · via DEV Community

Look. I’ve been breaking things since before it was normal for kids to have phones. I watched the entire security industry grow up from a hobby into a bloated bureaucracy of certifications, compliance checklists, and people who have never touched a soldering iron telling you what’s “secure.” And now, in 2026, we are facing a threat that nobody in any boardroom saw coming. Not because it is complicated. Because it is so damn elegant that the people paid to protect you simply cannot conceive of it.

Ultra-Wideband. UWB. The technology they sold you as the future of secure proximity authentication. The thing in your new phone, your smart car key, your office access badge. They told you it was unhackable because of how precisely it measures distance. Time-of-flight calculations, nanosecond-level timing, all that beautiful physics. And they were right. It is extremely hard to spoof. But “hard” is not the same as “impossible,” and the gap between those two words is where I live.

Let me tell you what is actually happening on the ground right now.

UWB Is Everywhere, and Nobody Understands It

By 2026, UWB is in everything. Apple has been shipping it since the iPhone 11. Samsung followed. Your Tesla uses it for keyless entry. Your BMW uses it. Your hotel room lock probably uses it. The entire “digital key” ecosystem that the industry bet billions on is built on UWB proximity verification. The idea is simple: two devices measure the time it takes for a signal to travel between them, and because radio waves move at the speed of light, they can calculate distance with centimeter-level accuracy. No relay attack possible, they said. The timing is too precise. You cannot fake it.

Except you can. You just cannot do it the way you would expect.

The attack surface is not in the protocol itself. It is in the implementation. And implementations are always, always messy. Every vendor has their own stack, their own quirks, their own shortcuts. The IEEE 802.15.4z standard that governs UWB security is a good foundation, but a foundation is not a house. And people have been building houses on it with no permits.

Here is what most security professionals do not understand. UWB security relies on a round-trip time-of-flight exchange. Device A sends a poll. Device B responds with a final message. The time difference, divided by two, multiplied by the speed of light, gives you distance. Beautiful. Elegant. And completely dependent on both devices being honest about when they sent and received the signal.

Now imagine you control the timing on one side. Not the content. Not the crypto. Just the clock.

The Relay Attack Evolved

Remember relay attacks? The old “grab the signal from your key fob and bounce it to your car” trick? UWB was supposed to kill that dead. And it did kill the old version. The naive version where you just amplified and retransmitted. UWB’s timing checks would catch that instantly. The time-of-flight would be wrong. Game over.

But here is what the researchers (and the less reputable ones) figured out. You do not need to relay the signal in real-time if you can manipulate the timestamp exchange itself. UWB devices authenticate by doing a round-trip time measurement. Device A sends a challenge. Device B responds. The time difference gives you distance. But what if you control both sides of that conversation? What if you are not relaying a signal, but relaying a whole authentication session, complete with fabricated timestamps that stay within the acceptable window?

This is what I call a “guided relay.” And it works. I have seen it work. Not in a lab. In the wild. At a conference. On someone’s car. In about four minutes with equipment that costs less than a decent laptop.

The beauty of it is that it does not require breaking the crypto. It does not require finding a zero-day. It requires understanding the protocol well enough to know exactly where the timing window allows for flexibility, and then exploiting that flexibility with precision. This is the kind of attack that a well-funded criminal organization could operationalize at scale by 2027.

The academic papers are starting to appear. I have read them. Most of them are cautious, hedged, full of “further research is needed.” That is academic speak for “we proved it works but we do not want to be the ones who get blamed when someone uses it.” I respect that instinct. But respect does not stop a thief.

Proximity Crimes: The New Physical Threat

Here is where it gets really ugly. UWB is not just for unlocking cars. It is being deployed for access control in buildings, for payment verification, for tracking high-value assets. And every single one of those use cases assumes that proximity equals intent. That if you are close enough, you are supposed to be there.

That assumption is now a vulnerability.

I call these “proximity crimes,” and they are going to explode in the next 18 months. The concept is simple: you do not need to be at the location. You need to be close enough to a device that is at the location, and you need to be able to speak its language. With UWB, “close enough” used to mean within a few centimeters. Now, with guided relays and UWB spoofing tools that are getting cheaper every quarter, it means within a few meters. Maybe even farther, depending on the implementation.

Imagine this. You walk past someone’s office. You are carrying a device in your pocket. Their UWB badge is on their desk. Your device queries it. Their badge responds. Your device now has a valid proximity token. You walk into the server room. The door thinks you are authorized. You walk out with whatever you want. Total time: under two minutes. No forced entry. No alarm. No evidence that anyone was ever there.

This is not science fiction. The tools to do this exist today. They are just not widely known, because the people who build them are not interested in writing blog posts about it. They are interested in using them.

And let me be clear about something. This is not going to stay in the hands of nation-states and organized crime forever. The hardware is cheap. The knowledge is spreading. By 2027, you will see this in insurance fraud. In corporate espionage. In petty theft at a scale we have never seen before, because the barrier to entry is dropping faster than any security team can adapt.

Why the Industry Is Sleeping

The security industry does not want to hear this. Not because they do not believe it, but because acknowledging it means acknowledging that the entire UWB trust model has fundamental flaws that cannot be patched with a firmware update. It means the billions spent on “secure” digital keys might be protecting nothing. It means the compliance frameworks, the certifications, the audits, all of it is built on a foundation that is cracking.

I have been saying this for years. The problem was never the technology. The problem is that we built an entire ecosystem of trust on assumptions that were never tested against someone who actually wants to break them. And now that someone is testing them, the results are not good.

The IEEE is working on updates. The FIDO Alliance is “reviewing” the standards. The car manufacturers are “assessing” the risk. You know what that means in real terms? It means they will form a committee, hold six meetings, publish a whitepaper, and then do absolutely nothing until someone loses a lot of money. Then they will panic. Then they will overcorrect. Then they will build something new that is just as broken in a different way.

I have watched this cycle repeat since the 1990s. It never gets old. It just gets more expensive.

What Actually Works (And What You Need to Know)

If you are a security professional reading this, your first instinct is probably to dismiss it. “We have mitigations.” “We have rolling codes.” “We have secondary authentication.” Sure. And I have bypassed every single one of those in my career, usually on the first try, usually with a device I built in an afternoon.

The truth is that proximity-based authentication was never a security control. It was a convenience feature that got rebranded as security because the marketing team needed a selling point. UWB made that convenience more precise. It did not make it more secure. Precision and security are not the same thing, and confusing them is the root cause of every major breach we will see in the next two years.

So what do you do? You stop trusting proximity. You add layers that do not depend on physics alone. You assume the attacker is already inside your timing window and you design accordingly. And most importantly, you get your hands dirty. You do not just read the spec. You build the attack. You see the signals. You understand what happens when the timing is off by even a few nanoseconds.

This is the part where I tell you about the stuff I have been building. Not because I need to sell you anything. I do not. But because I got tired of watching people read about attacks in academic papers and then act surprised when they see one in real life. If you want to actually understand how this works, you need tools. You need knowledge that does not come from a certification course. You need someone who has been on the wrong side of these networks for decades to show you the ropes.

If that sounds like you, I have put together a few things over the years that might help. Notes From the Wrong Side of the Network: Megapack I is everything I have learned about breaking wireless systems, all of it, no holds barred. It is the kind of knowledge they do not teach in any bootcamp because it would get the instructors fired.

Then there is the RollJam Construction and Operation guide. RollJam is one of the most elegant attacks in the RF world, and most people still do not understand it fully. I built a guide that takes you from concept to a functional prototype. Not theory. A working device. Because that is the only way you will ever truly understand it.

And if you want to get into the hardware side of things, the POCKET RECON: 75 ESP32 Projects for Wireless Research and Portable Hacking is exactly what it sounds like. Seventy-five projects. All built around the ESP32. All designed for someone who wants to actually do wireless research, not just read about it. Portable, powerful, and cheap enough that you can build five of them and still have money left for coffee.

I am not going to beg you to buy anything. I never do. But if you are reading this and you feel that itch, the one that tells you the official story is incomplete, then you already know what you need to do.

The Bottom Line

2026 is the year UWB’s dirty secret comes out. The relays work. The proximity crimes are real. And the people who were supposed to protect you are still arguing about whether the threat is “theoretical.” It is not theoretical. I have done it. Others have done it. The only question is whether you are going to be the one who understands it, or the one who gets caught by it.

The wireless world is not getting safer. It is getting more precise, which is not the same thing. And the people who understand that difference are going to have a very interesting next few years.

Choose wisely. And for God’s sake, stop trusting your proximity badge.

Sorry for the absolute shameless promotion in this post. To be completely real with you guys, I am facing homelessness and eviction and every penny counts right now. Please forgive my corpo-coded shilling. It's absolutely necessary for my survival.