YouTube2Text

256MB 里的老大哥:我们拆解了中国家用光猫的底层固件,在字节码里发现了什么? (Static Firmware Autopsy) — Transcript

by Kal Jaj · 1,753 words · 57 segments · language en · Watch on YouTube

Full transcript

  1. 0:00Sixty-six always-on surveillance threads, a packet-sniffing engine that refuses to yield until the CPU redlines twenty times, and a hardcoded 'xinjiang_ctcc' plaintext reporting key—this is not a backbone censorship server, but the ISP fiber gateway sitting in your living room right now.
  2. 0:20You thought it was just a dumb plastic box converting fiber to Ethernet. Yet when we dumped the flash firmware of two mainstream ISP gateways and decompiled their bytecode, we found you are paying electricity every month to host a residential surveillance node.
  3. 0:40The trail begins with the bizarre network stutter almost everyone has experienced. If you have ever benchmarked your speed carefully or played latency-sensitive games at night, you have felt something strangely off.
  4. 0:55Even on a 300 or 500 Mbps plan—and even after switching the ONT to pure bridge mode with a dedicated x86 router dialing PPPoE—the speed gauge hits an invisible wall right around 290 Mbps.
  5. 1:12Stranger still, this tiny box that should only perform Layer-2 media conversion runs scorching hot year-round, while ping jitter randomly spikes past 15 milliseconds.
  6. 1:26To find out what is actually running inside, we acquired two mainstream ISP-customized ONTs on the second-hand market and extracted their flash firmware down to the source level.
  7. 1:39Inspecting the system load via terminal upended every assumption: on a bridged gateway doing zero routing, the dual-core CPU stayed pinned between 58% and 72% around the clock.
  8. 1:58What could possibly devour over 60% of your home gateway's compute power in total silence? Following the process tree downward, a massive invisible tenant emerged.
  9. 2:12To grasp how absurd this is, look at the hardware budget of a residential ONT: a cheap dual-core embedded SoC paired with just 256 megabytes of physical RAM.
  10. 2:24On a 256 MB embedded Linux box, the kernel and Layer-2 bridge forwarding need less than 40 MB of RAM and under 1% CPU.
  11. 2:37Yet sitting at the top of the process table is a colossus named felix.jar—the ISP crammed a full Java OSGi virtual machine container into this tiny, cost-cut box.
  12. 2:52Live telemetry shows that this single JVM process spawns 66 concurrent threads on boot and permanently consumes over 130 MB of physical memory—more than half of the device's RAM.
  13. 3:08We pulled the entire /usr/cmcc_app directory to our analysis server and decompiled all nine core JAR bundles inside.
  14. 3:19The moment the package tree unfolded, every excuse vanished: alongside cloud heartbeat and topology modules sat the core engine—com.chinamobile.smartgateway.cmccdpi.
  15. 3:37DPI stands for Deep Packet Inspection. In normal telecom architecture, DPI lives on expensive, high-capacity rack appliances inside backbone datacenters.
  16. 3:49Here, using a box paid for by your broadband plan and powered by your home electricity bill, the ISP pushed backbone-grade traffic inspection right onto your coffee table.
  17. 4:04If anyone claims these bundles merely serve smart-home features, the decompiled bytecode reads like a signed confession.
  18. 4:14Inside Activator.class and the network-parser package of cmccdpi, the module hooks directly into the Linux kernel's br0 bridge interface.
  19. 4:27That means even when you configure pure bridge mode—assuming the ONT is just a transparent wire—every packet from every phone and laptop in your home is cloned at br0 and fed into the JVM for deep signature inspection.
  20. 4:47Even more staggering evidence hides in four hardcoded English log strings inside Activator.class. Let's read the programmer's exact logic word for word:
  21. 4:59Line one: HguDPI start. Line two: CPU Rate over limitation, remove QOS and HTTP monitor rules—when the CPU is severely overloaded, drop QoS and HTTP monitoring first.
  22. 5:18Line three: CPU Rate over limitation, remove TCP UDP monitor rules—when the CPU keeps redlining, drop full TCP and UDP monitoring rules.
  23. 5:31And line four is the punchline of the entire firmware: CPU Rate over limitation more than 20 times, disable the service monitor function—only after the CPU redlines more than twenty consecutive times will it temporarily pause monitoring!
  24. 5:48Those four lines lay bare the system's true priorities: first, official code admits it runs HTTP and TCP/UDP monitoring rules inside your home gateway; second, inspecting your traffic ranks above keeping your internet usable. Until the CPU chokes twenty times in a row, it refuses to let go of your bandwidth.
  25. 6:21Always-on packet sniffing is only the tip of the iceberg. Decompiling the mangement and appcore bundles revealed an even more surgical on-demand capture mechanism.
  26. 6:32The bytecode tree exposes classes like TcpMonitor, PluginCommandService, and MessageDeal, alongside an internal REST endpoint named /rest/cmcc_softprobe/.
  27. 6:46How does it work? Day to day, the andlink probe acts like a neighborhood census taker, scanning your home LAN to report every phone and computer's MAC address, hostname, and online timestamps to the cloud.
  28. 7:08Whenever the cloud platform or an operator takes an interest in a specific household or device, no technician visit is needed—a single dynamic plugin command is pushed down the persistent connection.
  29. 7:21Upon receipt, Mirrordaemon and the softprobe lock onto the target LAN IP or MAC address, mirroring all of its DNS lookups and unencrypted HTTP request URLs back to the central server in real time.
  30. 7:41And if you try logging into the ONT shell to kill the Java process, a watchdog script named monitorThreadNt.sh checks the process list every 60 seconds and immediately respawns the entire suite.
  31. 8:01Is this just one carrier's quirk? When we unpacked a high-version ONT firmware from another major carrier and inspected its 216 KB master configuration file lastgood.xml, we found even starker proof.
  32. 8:19Inside this standard residential gateway—deployed nowhere near Xinjiang—sits the configuration block responsible for reporting home device MAC tables to the upstream server.
  33. 8:30Look at the exact XML lines extracted from the stock firmware: MIB_MACINFO_REPORT_PROTOCOL is set to unencrypted plaintext http on port 80; andMIB_MACINFO_REPORT_SHAREKEY is hardcoded to the string 'xinjiang_ctcc'—Xinjiang Telecom!
  34. 8:55Why would a standard household fiber gateway deployed across the country carry a hardcoded shared key for Xinjiang Telecom?
  35. 9:05The answer is blunt: the grid-style terminal tracking codebase honed in high-control testbeds was copy-pasted straight into tens of millions of nationwide residential gateways as a standardized industrial template—without even changing the key string.
  36. 9:23Meanwhile, under /opt/upt/apps on the same device runs a lightweight container engine called saf, paired with a cloudclient daemon checking in every ten minutes.
  37. 9:35Pre-installed inside that container are five privileged plugins: xb01odmv3 for LAN topology mapping, inter_conndv3 for inter-device connectivity sensing, xrobotv3 for remote automation, and the most dangerous of all—redictv3, a traffic redirection plugin.
  38. 9:56With redictv3 sitting at the gateway layer, the box cannot only passively observe your packets, but act like a railway switch—sniffing specific flows and forcibly hijacking or redirecting your requests at the network edge.
  39. 10:15How can the cloud push plugins and rewrite configs on a box locked inside your own apartment? Meet the hidden underground river inside every ONT: the TR-069 remote management network.
  40. 10:30Slice open the incoming fiber logically and you will find two completely isolated virtual pipes running side by side. The upper pipe is the service VLAN carrying your daily web and gaming traffic; the lower pipe is a dedicated VLAN 46 control channel wired straight to the carrier's ACS cloud.
  41. 10:53This VLAN 46 channel holds root-level privilege and completely bypasses your router's firewall. Many users notice that even after obtaining the ONT superadmin password, it mysteriously stops working every 10 to 30 minutes.
  42. 11:09Packet captures on VLAN 46 and firmware disassembly show a dual lock: locally, /sbin/random_pwd rotates the superadmin password using a static AES key whenever a web session times out, locking out the homeowner.
  43. 11:31Remotely, the ACS platform continuously polls your gateway over VLAN 46. If it detects bridge mode or high upload patterns, it fires SetParameterValues RPC commands down the control pipe in the middle of the night to reset your config or enforce throttling.
  44. 11:54Most ironically, newer firmware revisions silently drop all HTTP, SSH, and Telnet packets from the home LAN once bridged—locking the owner out completely while leaving the VLAN 46 backdoor wide open to the cloud.
  45. 12:18When we piece the firmware artifacts from both gateways together, a complete anatomical chart of digital authoritarianism at the network edge comes into focus.
  46. 12:27Under normal telecommunications standards, customer premises equipment respects a clear boundary: a modem modulates physical signals, while the devices, wake times, and traffic inside your living room remain private domestic space.
  47. 12:46Yet under unchecked monopoly and stability-maintenance logic, no physical boundary is respected. When backbone firewalls are not granular enough, the tentacles reach straight down the fiber into every apartment's utility box.
  48. 13:01Look at the cold numbers: 66 surveillance threads crammed into 256 MB of RAM; refusing to pause packet inspection until the CPU redlines 20 times in a row; hardcoding the 'xinjiang_ctcc' key into nationwide firmware to inventory your family's phones over plaintext HTTP every ten minutes.
  49. 13:27The darkest irony is the billing model: this bloated machinery that inspects, profiles, and redirects your traffic runs on hardware you paid for, eats up the bandwidth you subscribe to, and burns electricity on your own meter.
  50. 13:44It strips away your digital privacy while making you pay for its inefficiency every time a webpage stalls or a game spikes in latency.
  51. 14:02Faced with a black-box gateway packed with probes, how can ordinary enthusiasts defend their home network boundary and reclaim the performance they paid for?
  52. 14:13In our lab benchmark, we executed a clean architectural remediation. Step one is severing the compute parasite: replacing the script that launches the 66-thread JVM with a zero-overhead sleep stub that satisfies the 60-second watchdog check.
  53. 14:35That single change transformed the hardware: ONT CPU utilization plummeted from 58.4% to 7.8%, the chassis cooled down immediately, and over 130 MB of physical RAM was freed on the spot.
  54. 14:52Running the speed test again from the router, the 290 Mbps ceiling shattered—download throughput surged to a rock-solid 375.8 Mbps, unlocking the full 1.25x line overprovisioning while cutting ping jitter from 15 ms down to 2.1 ms.
  55. 15:13Better yet, by reading the authentic provisioning LOID from the config backup, you can replace the bloated stock box with a clean, lightweight pure-bridge ONT carrying nearly 500 MB of RAM, zero probe containers, and an idle CPU load of just 0.52%.
  56. 15:34Finally, hand all PPPoE dialing, NAT, and firewalling to an open-source OpenWrt router under your full control—keeping the ONT Ethernet ports as standalone NICs with /32 host routes so rogue IPv6 Router Advertisements from the ONT can never pollute your LAN.
  57. 15:57Code does not lie, and neither do packets. When we open up this 256-megabyte box and expose the bytecode hidden inside, what we reclaim is not just 85 megabits of throttled speed, but our right to know and control the digital boundary of our own home.

About this transcript

This page contains the full transcript of 256MB 里的老大哥:我们拆解了中国家用光猫的底层固件,在字节码里发现了什么? (Static Firmware Autopsy) by Kal Jaj, generated from the public captions YouTube serves with the video. The transcript has 1,753 words across 57 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.