Latest / Dark Perimeter: Real Breaches, Real Stakes / Fifteen Minutes to Root
Transcript
- 0:00SPEAKER_01: Sometime in the middle of October, a code repository crossed forty-one thousand stars in under 10 days.
- 0:08SPEAKER_01: It ships no installer.
- 0:10SPEAKER_01: It has no binary.
- 0:12SPEAKER_01: The entire product is a block of text you paste into an AI coding agent, and about 15 minutes later, your television has stopped showing you ads.
- 0:22SPEAKER_01: By version 3, it covered roughly 300 models across 83 brands, with more than 600 people contributing.
- 0:31SPEAKER_01: In the same four weeks, a separate advisory landed, describing a chain of three flaws that let somebody on your local network take root on an LG set with no PIN, no prompt, and nothing at all required from the person holding the remote.
- 0:46SPEAKER_01: Same device, two very different hands on it.
- 0:49SPEAKER_01: I am Cole Drayden, and tonight we are going to spend real time on both of those.
- 0:55SPEAKER_01: Because I think this is the most important consumer security story of the year and almost nobody is treating it like one.
- 1:04SPEAKER_01: With me, Dr.
- 1:05SPEAKER_01: Elliot Vance and Marcus Hale.
- 1:09SPEAKER_00: It is worth being precise about what the owners are actually doing because the phrase going around is hacking your television, and that is not quite it.
- 1:16SPEAKER_00: The main project works over Android Debug Bridge across the network.
- 1:20SPEAKER_00: You enable developer mode on the set, the agent finds the television on your own Wi-Fi, enumerates the installed packages, asks you which ones you actually use, and then disables the rest in the user profile.
- 1:32SPEAKER_00: It also replaces the launcher, the home screen, with something small and quiet.
- 1:36SPEAKER_00: On the first widely shared run, the developer removed 25 vendor packages from a Xiaomi set, and the agent wrote a new launcher from scratch.
- 1:44SPEAKER_00: No route required.
- 1:45SPEAKER_00: Nothing is actually uninstalled from the system partition.
- 1:49SPEAKER_02: Which matters more than people realize.
- 1:51SPEAKER_02: Disabled in the user profile is a reversible state, not a removal.
- 1:55SPEAKER_02: The firmware still has the code, the vendor still ships updates, and when an update lands, your television can quietly restore the packages and the telemetry along with them.
- 2:03SPEAKER_02: The project knows this, by the way.
- 2:05SPEAKER_02: There is a tool in it that detects when the vendor has put everything back and reapplies your changes.
- 2:10SPEAKER_02: That tells you something about the actual relationship here.
- 2:12SPEAKER_02: This is not a one-time modification.
- 2:14SPEAKER_02: This is an ongoing negotiation with a device you supposedly bought.
- 2:18SPEAKER_01: Let me stay on the human side for a second, because the origin story is the part I keep thinking about.
- 2:26SPEAKER_01: One developer got tired of the ads on his parents' television.
- 2:30SPEAKER_01: He pointed a coding agent at it, and the whole thing took an afternoon.
- 2:35SPEAKER_01: His post about it did somewhere north of eight and a half million views.
- 2:40SPEAKER_01: Another person replaced a 192-megabyte stock launcher with an 83 megabyte one he had written that day.
- 2:49SPEAKER_01: A third sent an agent his television's model listing and asked, essentially, can this be hacked?
- 2:57SPEAKER_01: And then shot video of the interface afterward because it was finally fast.
- 3:02SPEAKER_01: Elliot, nothing in that paragraph is a new capability.
- 3:07SPEAKER_01: Why October?
- 3:09SPEAKER_00: Because the skill floor collapsed.
- 3:11SPEAKER_00: Every piece of this was possible in 2015.
- 3:14SPEAKER_00: The debug bridge, the package manager, the custom launcher, all of it.
- 3:18SPEAKER_00: What you needed was someone who knew which of 400 packages was load-bearing, who could read a log cat when the set wouldn't boot, and who was willing to spend a weekend finding out.
- 3:28SPEAKER_00: That person existed in the thousands.
- 3:30SPEAKER_00: Now the knowledge is in the agent, and the asking price is a paragraph of English.
- 3:34SPEAKER_00: That is the whole story.
- 3:35SPEAKER_00: The tooling did not get better.
- 3:37SPEAKER_00: The population of people who can use the tooling went up by three or four orders of magnitude.
- 3:42SPEAKER_02: And notice that it only worked on one half of the market.
- 3:45SPEAKER_02: Android and Google TV speak the debug bridge.
- 3:48SPEAKER_02: So Sony, TCL, Philips, HiSense, Xiaomi, the Shield, the Fire sets with some fighting.
- 3:53SPEAKER_02: Samsung's Tizen and LG's Web OS do not, and neither does Roku, Visio, or Hisense's own platform.
- 3:59SPEAKER_02: For those you need actual route, and that is a completely different conversation.
- 4:02SPEAKER_02: The Samsung routing work this year is real research.
- 4:05SPEAKER_02: There is a package name injection in the debug service that gets you a low privilege foothold, then a physical memory bug on one panel generation and a GPU driver bug on another to get you the rest of the way.
- 4:16SPEAKER_02: That is not fifteen minutes.
- 4:17SPEAKER_02: That is somebody who knows what they are doing, spending a day on the first set and three hours on the second once they had the pattern.
- 4:24SPEAKER_01: Which is itself a finding.
- 4:26SPEAKER_01: Three hours.
- 4:28SPEAKER_01: Marcus, you and I have both sat through vendor conversations where the answer to a hardware security question was essentially nobody is going to bother.
- 4:38SPEAKER_01: Hold that thought because I want to do the why before we do the risk.
- 4:44SPEAKER_01: Elliot, make the case for the people doing this.
- 4:48SPEAKER_01: What is actually on these televisions that is worth this much trouble?
- 4:53SPEAKER_00: Automatic content recognition, mostly.
- 4:55SPEAKER_00: The mechanism is simple.
- 4:56SPEAKER_00: The television samples what is on the screen or coming out of the speakers, fingerprints it, and sends the fingerprint off the set to be matched.
- 5:03SPEAKER_00: That tells a third party what you watched, when, for how long, and on which input.
- 5:08SPEAKER_00: A measurement study out of University College London and UC Davis, presented at the ACM Internet Measurement Conference, went through this carefully.
- 5:16SPEAKER_00: Two findings stand out.
- 5:17SPEAKER_00: The first is that recognition is on by default when you set the setup, and turning it off takes several clicks spread across multiple advertising and tracking submenus, which the authors described as extremely difficult for a typical user to exercise.
- 5:31SPEAKER_00: The second is that it does not only watch the television's own apps, it can capture content coming in from an external device.
- 5:38SPEAKER_01: Say that second part again slowly, because that is the one that lands with people.
- 5:44SPEAKER_00: If you plug a laptop into the television and use it as a monitor, the recognition system is still sampling the screen.
- 5:50SPEAKER_00: Separate work involving researchers at Carlos III University of Madrid reported the same thing, viewing data collected even when the set is used purely as an external display.
- 6:00SPEAKER_00: I will put one caveat on the numbers you may see quoted.
- 6:03SPEAKER_00: The configuration file on one vendor's set lists a 48 kilohertz sample rate, and that has been reported in places as 48,000 snapshots per second.
- 6:12SPEAKER_00: 48 kilohertz is a perfectly ordinary audio sampling rate.
- 6:16SPEAKER_00: It almost certainly describes how the audio is captured, not how often a fingerprint goes out the door.
- 6:21SPEAKER_00: The research team was careful, the retelling has not always been.
- 6:24SPEAKER_00: The honest version is still bad enough.
- 6:26SPEAKER_00: The sampling is continuous, the payloads are encrypted, so nobody outside the vendor knows exactly what is in them.
- 6:32SPEAKER_00: And when the researchers filed formal data access requests under European law, the responses came back vague and contained far less data than the volume they had actually measured leaving the device.
- 6:44SPEAKER_02: And that is the part that moves this out of privacy and into security for me.
- 6:48SPEAKER_02: A device on your network running software you did not choose, continuously sampling a sensor, encrypting the result, and shipping it to infrastructure you cannot audit, with a vendor that cannot or will not tell you what is in it.
- 6:59SPEAKER_02: If a contractor plugged that into your network, you would write it up as a finding.
- 7:03SPEAKER_02: We let it in the building because it has a picture on it.
- 7:06SPEAKER_01: So let us do the security balance sheet, honestly.
- 7:08SPEAKER_01: Both columns.
- 7:10SPEAKER_01: Marcus, you first, upside.
- 7:13SPEAKER_02: The upside is real, and I do not want to hedge it into nothing.
- 7:16SPEAKER_02: Attack surface reduction is the oldest control we have.
- 7:19SPEAKER_02: Twenty-five fewer packages means fewer services, fewer listeners, fewer update channels, fewer third-party software development kits with network access, and a smaller blast radius when one of them turns out to be bad.
- 7:30SPEAKER_02: Less outbound traffic means less data in motion to be intercepted, leaked, or subpoenaed.
- 7:35SPEAKER_02: A smaller launcher is a smaller thing to exploit.
- 7:37SPEAKER_02: The recovery story is also better than the usual modding scene.
- 7:40SPEAKER_02: The changes are reversible.
- 7:42SPEAKER_02: The project writes a recovery script before it touches anything, and the floor is a factory reset from the recovery menu rather than a paperweight.
- 7:49SPEAKER_00: I would add that it changes who holds the decision.
- 7:52SPEAKER_00: Today the vendor decides what runs on the set forever, including after they stop shipping security updates.
- 7:58SPEAKER_00: A television has a 10-year service life and a four-year support window.
- 8:02SPEAKER_00: And at the end of that window, the vendor's answer is buy a new television.
- 8:06SPEAKER_00: An owner who can remove software can keep an unsupported device useful without keeping it dangerous.
- 8:12SPEAKER_00: That is not a small thing.
- 8:14SPEAKER_00: That is the only sustainable answer anyone has offered to the unpatchable endpoint problem in consumer hardware.
- 8:20SPEAKER_01: Alright.
- 8:22SPEAKER_01: Downside.
- 8:23SPEAKER_01: And Marcus, I want you to be specific because I think there are three separate risks here that keep getting mashed into one.
- 8:32SPEAKER_02: Three is about right.
- 8:34SPEAKER_02: The first is the method.
- 8:35SPEAKER_02: To do this over the network, you turn on the debug bridge, which means a service that accepts commands and runs them on the device, listening on your network.
- 8:42SPEAKER_02: The project tells you to close it afterward, and that advice is in the documentation, and plenty of people will not read that far or will not know how.
- 8:49SPEAKER_02: An exposed debug bridge is not a theoretical risk.
- 8:52SPEAKER_02: It is the single most reliably abused foothold in the Android device ecosystem.
- 8:56SPEAKER_02: There is an Android botnet tracked publicly since late last year, whose primary vector is exactly that scan for the debug port, push a payload, and roll the device.
- 9:04SPEAKER_02: The research teams counting it put confirmed infections in the high hundreds of thousands to over a million devices in a single snapshot, with the devices resold as residential proxy exit nodes at around twenty cents a gigabyte, plus credential stuffing and some record setting denial of service volume.
- 9:19SPEAKER_02: I will say clearly that most of those are gray market television boxes that shipped with debug wide open, not somebody's living room set that was open for 15 minutes.
- 9:27SPEAKER_02: But the mechanism is identical, and the window is whatever the owner leaves it.
- 9:31SPEAKER_02: The second trust in the agent.
- 9:34SPEAKER_02: The agent decides what to disable.
- 9:36SPEAKER_02: You are approving a list you cannot evaluate, generated by a model, against a package namespace you have never seen on a device with no serial console.
- 9:44SPEAKER_02: People have reported bootloops, at least one person bricked a set, and the failure mode that worries me is not the obvious one.
- 9:50SPEAKER_02: It is the quiet one.
- 9:51SPEAKER_02: The agent disables something that looked like bloatware and was actually the update service, and now your television never gets another security patch and nothing on screen tells you.
- 9:59SPEAKER_00: Which is a genuinely new category of error.
- 10:02SPEAKER_00: A human moder who disables the update service usually knows they did it.
- 10:06SPEAKER_00: A model that disables it while cheerfully reporting success has produced a silent downgrade of the device's security posture, and the owner's mental model is now wrong in a way that will not be corrected for years.
- 10:38SPEAKER_02: By an agent that is specifically designed to improvise around ambiguity.
- 10:42SPEAKER_02: Paste this into your agent as curl pipe bash with extra steps and worse provenance.
- 10:46SPEAKER_02: The project appears to be run in good faith, and I have no reason to think otherwise.
- 10:50SPEAKER_02: That is exactly why it is a good illustration.
- 10:52SPEAKER_02: The honest version of this already has no supply chain integrity, so the dishonest version has nothing to defeat.
- 10:58SPEAKER_01: Alright.
- 10:59SPEAKER_01: Now let me turn the television around, because the other half of this month is the part that should worry people more.
- 11:06SPEAKER_01: Elliot, walk through the WebOS chain, because the shape of it is the lesson.
- 11:13SPEAKER_00: A researcher demonstrated it at an offensive security competition in Seoul in the spring and placed third in the WebOS category.
- 11:20SPEAKER_00: The advisory went public on the 12th of October.
- 11:23SPEAKER_00: It chains three flaws.
- 11:24SPEAKER_00: The attacker is on the same local network.
- 11:26SPEAKER_00: They reach a pairing service that the vendor's phone app uses.
- 11:30SPEAKER_00: They replay a manifest from a demo application that ships in the firmware, signed with a test certificate the firmware trusts.
- 11:37SPEAKER_00: One permission in that replayed manifest causes the pairing service to skip the PIN prompt and hand over a privileged key.
- 11:44SPEAKER_00: With the key, they launch another built-in application and point it at a page they control because that application never validates where it is being sent.
- 11:52SPEAKER_00: The page keeps access to an internal bridge into system services.
- 11:56SPEAKER_00: Through the bridge, they reach the logging daemon which takes an unvalidated field, and the logging daemon runs as root.
- 12:03SPEAKER_00: So root on the television from the network with no pin and no interaction from the owner.
- 12:08SPEAKER_01: No interaction.
- 12:10SPEAKER_01: That is the sentence.
- 12:12SPEAKER_00: No interaction.
- 12:13SPEAKER_00: Two things to say fairly.
- 12:15SPEAKER_00: It is local network only, not internet facing, and the vendor has shipped a fix, so the action for an owner is to update.
- 12:22SPEAKER_00: Also, no identifiers were assigned to the individual flaws.
- 12:26SPEAKER_00: And the demonstration was on two inexpensive sets on one firmware line.
- 12:30SPEAKER_00: So how broadly it applies is genuinely unknown rather than known wide.
- 12:34SPEAKER_00: But look at what carried the chain: a test certificate in production firmware, a demo app nobody removed, an application that trusts any navigation target.
- 12:43SPEAKER_00: A root logging demon that takes unsanitized input.
- 12:46SPEAKER_00: Every one of those is a 2008 finding, shipped in 2026, in a television, behind a signed boot chain that was supposed to make all of it unnecessary.
- 12:55SPEAKER_02: And that is why I do not accept the framing that owner routing is what makes these devices unsafe.
- 13:01SPEAKER_02: The owners are exploiting the same weaknesses the attackers are.
- 13:04SPEAKER_02: Those weaknesses are already there.
- 13:05SPEAKER_02: The deep loading movement did not create them.
- 13:07SPEAKER_02: It revealed them to a much larger audience, which, if you believe in disclosure at all, is how this is supposed to work.
- 13:13SPEAKER_02: The uncomfortable implication is the one vendors will not say out loud.
- 13:16SPEAKER_02: The reason your television has not been attacked much yet is not that it is hard, it is that it was not worth anyone's time.
- 13:23SPEAKER_02: Two and a half hours per panel generation changes that math.
- 13:26SPEAKER_01: Let me bring this into the enterprise, because most of our listeners are going to have to answer for this in a meeting.
- 14:03SPEAKER_02: Step two is network placement.
- 14:05SPEAKER_02: These go on an isolated segment with no rote to anything that matters, and an egress policy, because the default behavior of the device is to phone out constantly.
- 14:13SPEAKER_02: Step three is a procurement question nobody asks, which is how long will this model receive security firmware, and then a lifecycle decision that is driven by that date rather than by whether the picture still works.
- 14:24SPEAKER_02: Step four, and this is cheap and nobody does it, is to go look at whether developer mode or the debug bridge is enabled on any of them right now.
- 14:31SPEAKER_02: In a building where audiovisual contractors have been in and out for five years, I would not assume.
- 14:36SPEAKER_00: I would add the microphone and camera question to the procurement list and the recognition question.
- 14:41SPEAKER_00: If the set is sampling the screen and shipping fingerprints, and the screen in that room is sometimes somebody's laptop displaying an unreleased financial statement, you have an information flow that your data protection program has never seen and cannot describe.
- 14:54SPEAKER_00: Whether anything bad happens with it is a separate question from whether you can account for it.
- 14:59SPEAKER_00: You cannot.
- 15:00SPEAKER_01: And there is a second enterprise angle, which is your own people doing this at home.
- 15:05SPEAKER_01: Marcus?
- 15:07SPEAKER_02: Right, and I want to be careful not to be the department of no about it, because I think most of them are improving their situation.
- 15:13SPEAKER_02: The practical exposure is that the home network now has a television with debug services that were turned on by an agent and may not have been turned off, on the same flat network as a corporate laptop.
- 15:23SPEAKER_02: For most organizations, that is an acceptable risk with a zero trust posture and full disk encryption and a managed endpoint, and it is an unacceptable risk if you are still treating the corporate network perimeter as the control.
- 15:34SPEAKER_02: The honest guidance to employees is short.
- 15:36SPEAKER_02: If you do this, close the debug access when you are done, and keep your work device on a different network segment than your experiments.
- 15:46SPEAKER_01: Because I do not think this ends at televisions.
- 15:50SPEAKER_00: It does not.
- 15:51SPEAKER_00: And the reason is that televisions are not special.
- 15:53SPEAKER_00: They are simply the most advanced case of a pattern that is now in almost everything.
- 15:58SPEAKER_00: A device sold at a thin hardware margin, subsidized by a software and advertising business that runs on the customer afterward.
- 16:05SPEAKER_00: That shape is in cars, in appliances, in printers, in routers, in the screens on exercise equipment.
- 16:12SPEAKER_00: The incentive to put advertising and data collection into a device you already paid for does not stop at the one with the biggest screen, and neither will the response.
- 16:21SPEAKER_00: What changed in October is not that people want to remove vendor software.
- 16:25SPEAKER_00: They have always wanted that.
- 16:26SPEAKER_00: What changed is that the capability became conversational.
- 16:31SPEAKER_02: And the vendor response is predictable because we have watched it happen in phones twice.
- 16:35SPEAKER_02: It is attestation, remote attestation, locked bootloaders, server-side feature gating, where the thing you removed locally is now required to be present before the streaming service will hand you a license.
- 16:45SPEAKER_02: They will not frame it as locking you out.
- 16:47SPEAKER_02: They will frame it as security, and part of the argument will be true, which is what makes it effective.
- 16:51SPEAKER_02: A set that cryptographically proves its software is unmodified before it plays anything is genuinely harder for a botnet to enroll, and it is also a device you can never clean out.
- 17:00SPEAKER_02: We are going to spend the next five years arguing about that trade-off, and the arguing will be better if people understand that both halves of it are real.
- 17:08SPEAKER_00: There is also a legal layer, and I am not a lawyer, and this is not legal advice.
- 17:12SPEAKER_00: But it is worth knowing that modifying firmware on a device you own sits in genuinely contested territory, that the rules differ by country and by device category, and that the exemptions carved out for repair have historically been narrow, temporary, and argued over every three years.
- 17:29SPEAKER_00: Anyone building a business on top of this should get actual counsel.
- 17:33SPEAKER_00: Anyone doing it to their own television in their own living room is in a different position than anyone distributing tools to do it at scale.
- 17:41SPEAKER_01: Let me try to land this.
- 17:43SPEAKER_01: Here is what I think we actually learned this month.
- 17:48SPEAKER_01: First, the capability floor for modifying consumer hardware has dropped to the price of a paragraph, and that is permanent.
- 17:56SPEAKER_01: The agents are not getting worse at this.
- 17:59SPEAKER_01: Second, that cuts in both directions by exactly the same mechanism, and anyone selling you the version where it only cuts one way is selling you something.
- 18:10SPEAKER_01: Third, the televisions were already soft.
- 18:14SPEAKER_01: A test certificate in shipping firmware and a root logging daemon that eats unsanitized input are not consequences of the deep loading movement.
- 18:24SPEAKER_01: They are what the deep loading movement walked past on its way in.
- 18:29SPEAKER_01: Fourth, and this is the one for the people in our line of work.
- 18:34SPEAKER_01: The device nobody owns, on the network nobody segmented, with the support window nobody checked, is now interesting to attackers in a way it was not eighteen months ago.
- 18:46SPEAKER_01: And the thing that made it interesting was a productivity improvement.
- 18:51SPEAKER_00: I would put one more alongside that.
- 18:53SPEAKER_00: The ownership question is not sentimental.
- 18:56SPEAKER_00: Security requires the ability to remove software.
- 18:59SPEAKER_00: And for 30 years, we have been building a consumer market in which that ability is being engineered away for reasons that are partly legitimate.
- 19:06SPEAKER_00: You cannot secure what you cannot modify, and you cannot trust what you cannot inspect.
- 19:12SPEAKER_00: Whatever settlement comes out of the next few years has to leave the owner some version of both.
- 19:17SPEAKER_00: Or we are going to keep shipping hundreds of millions of devices that are perfectly protected against their owners and wide open to everyone else.
- 19:38SPEAKER_01: That is the homework.
- 19:40SPEAKER_01: Elliot, Marcus, thank you both.
- 19:42SPEAKER_01: This is Dark Perimeter.