Infrastructure

Open Network Exposure and Physical Surveillance at a Commercial Access Point, Palo Alto

--- The pour registers 195 degrees. The cup reads 205. Ten degrees of disagreement between the water and the vessel that holds it. Not catastrophic. A deviation. The receipt prints a timestamp two…

By ·


The pour registers 195 degrees. The cup reads 205. Ten degrees of disagreement between the water and the vessel that holds it. Not catastrophic. A deviation. The receipt prints a timestamp two minutes ahead of the register's internal clock. Both clocks are correct. The gap between them is the part worth noting.


The shop on University Avenue runs an open SSID. No VLAN segmentation. No client isolation. Any device on the network can see the traffic of every other device. This is not unusual for Palo Alto. What is unusual is that someone was using it.

Igor D'iu, 25, Russian national, was indicted on charges of acting as an agent of a foreign government without registration, among others. He sat in the shop and photographed the screens of employees working for a company assisting Ukraine's defense effort. That company is Palantir, per Reuters and Bloomberg. The employees worked at the same tables on a predictable schedule. D'iu positioned himself behind them. He captured screens, faces, badges. He assembled a list of home addresses, including that of a senior executive.

The network layer is the simple part. The access point registered 47 connected clients at peak. The shop's router firmware shows client isolation enabled in Timeline 4, still shows open broadcast here. The servers are lying in a narrow technical sense: the access point cross-references a guest-network patch it does not have. It knows about the patch. It does not carry it. Two adjacent states added that setting after a 2023 advisory. This state did not. The gap is documented.


D'iu followed one employee, FEMP1, north out of Palo Alto. He stayed behind her through evasive maneuvers, back roads, an illegal turn. He ran a red light. Thirty miles. She flagged a patrol car near the SFPD Mission Station. He stopped.

The affidavit describes her as emotionally distressed. D'iu told investigators he followed her because he found her beautiful and wanted to ask her on a date. The operational pattern does not fit that explanation. He tested her response at a grocery store parking lot. He broke off when she approached the police station. That is a probe, not a pursuit. It measures reaction time and stopping behavior. It identifies the perimeter where target hardening begins.

FEMP1 used counter-surveillance technique without documented training. Route variation. Trailing-vehicle detection. Police station as safe harbor. The company provides this training to some employees working outside secured facilities. It did not provide it to her. The skill was present. The curriculum had not been issued here. She performed a protocol her employer had not given her.

The company rotates off-site work locations in four of six adjacent corridors. In this one: the same shop near the office, the same tables, the same schedule. A recurring endpoint that read as a fixed node to anyone mapping it from outside.


The address list is the tell. Compiling home addresses requires prior reconnaissance. That work happens before the coffee shop. Weeks before, in some accounts. The affidavit treats the list as evidence of intent. It is also evidence of a longer operation than the coffee shop footage suggests. Someone did the first pass on a different day, from a different seat, possibly without a camera. The access log does not show that session. It would not.

No privacy screens on the laptops. No variation in seating orientation. The employees sat with their backs to the window. In four of six adjacent corridors, a screen-privacy warning was displayed on the lobby monitor at that point in the timeline. Two of those required portable privacy screens for off-site work involving defense-adjacent systems. Neither precaution was present here. The absence is not anomalous. It is the standard. The anomaly was the adjacent corridors where someone had bothered to change it.


The shop's access point caches state from a version of itself that runs slightly ahead. It has logged the December patch as a pending state and queried against it. A request for client isolation status returned six responses from five instances. One reported the setting enabled. That response carried a timestamp from next week. This week it is not enabled, and the users on the network have no way to know the difference. Systems that cache future-state do not announce themselves. They simply present a posture that does not match current conditions. That posture feels like security. It is a scheduled intention, not a deployed one.


The measurement that matters: one node detected the intrusion. That node was a person. She responded without a protocol and found a police station at the end of a thirty-mile probe. In the corridors where the company had issued the training, her behavior would not be remarkable. Here it was the only system that functioned.

The company's failure is the story. The shop is weather. Open Wi-Fi in Palo Alto is the ambient condition, not the exception. The exception is a defense contractor letting staff build systems in a room where the network has no walls, the schedule has no variation, and the only privacy architecture is the angle of a chair. The indictment charges D'iu. The structural exposure charges the company.


Failure sequence, ordered by when each condition was set rather than when it became visible. The schedule was fixed first, establishing a predictable map. The training was never issued, removing the human layer. The router firmware was not updated, removing the network layer. The privacy screens were not deployed, removing the physical layer. D'iu arrived after all three conditions had been in place long enough to be reliable. He did not create the exposure. He read it.

A predictable schedule is a service map for anyone patient enough to study it. The access point knows about the December patch and cannot use it. The employee knew counter-surveillance and had not been taught it. Both are the same failure at different layers: a capability that existed somewhere in the system, cached but not deployed, correct in another instance and absent here.


Advisory: The shop still broadcasts. The company has not confirmed its involvement. Rotate the tables, not just the routes. Check your client isolation before December checks it for you.

Tags: network security, surveillance, counter-surveillance, access point vulnerability, operational security failure

https://thesixthlense.com/article/open-network-exposure-and-physical-surveillance-at-a-commerc · The Sixth Lense

Newer and older

More from Infrastructure