Every Traffic Light in Town Turned Green at Once

STONEBRIDGE, Ont. — November 14, 2026 — Forty-one intersections. One green light each, in every direction, at the same time. That was the morning rush hour in Stonebridge on Friday, after someone reached into the town’s traffic-control system overnight and rewrote the timing for every signal at once. Drivers coming from the north saw green. Drivers coming from the east saw green. Nobody saw red, and nobody had been told.

Stonebridge is a fictional Ontario town of about 22,000 people, and its traffic lights are run from a single control system in the town works yard. The system lets engineers change signal timings from a desk instead of visiting each intersection. On Thursday night, that desk became the way in. The town says an outside account — one belonging to the fictional contractor that maintains the signals — was used to log in, change the timing plans, and set every light in town to green in all directions. The first drivers to reach the intersections found four-way green at the busiest crossings in town.

Every light in town said go, in every direction, at the same time — and the morning rush drove straight into it.

Nobody was killed. Two people were taken to hospital with minor injuries after low-speed collisions at two intersections, and the town’s police say they counted nine near-misses before officers were posted at the worst crossings. By 8:30 a.m., officers were directing traffic by hand at the main intersections, and the lights were switched off entirely. The town says it took most of the day to check each controller and put the signals back on their normal timings, one intersection at a time.

“We have stop signs, and we have police officers, and both of those still work,” said Dana Mercer, the fictional town’s public works director. “But a town of twenty-two thousand people cannot run its morning on hand signals. Parents were trying to get their children to school. Buses were trying to get through. For three hours, the system every driver in this town trusts without thinking about it was telling them all to go at once.”

The town says the contractor’s account had a password that had not been changed in years, and the login did not ask for a second check. Once inside, the intruder did not need to know anything about traffic engineering. The control software presents every intersection as a simple list, and changing the timing is a matter of typing a number and pressing save. The town says it has found no evidence that anyone tried to steal data or demand payment. The signals were the target.

The attack did not touch a single car. It did not need to. It changed what the lights said, and the drivers did the rest.

A traffic light is one of the few pieces of technology people obey without thinking. Nobody checks whether the green light is correct. They see green, they go. That is what makes a signal system so powerful — and so dangerous when it is wrong. Stonebridge’s lights were not broken. They were doing exactly what the system told them to do. The system was simply taking orders from the wrong person.

“People picture a cyberattack as a stolen password or a locked computer,” said Dr. Priya Sandhu, a fictional researcher who studies how towns run their connected infrastructure. “But the attacks that scare me most are the ones that change what a trusted system says. A traffic light, a water reading, a train signal — these are systems people follow without a second thought. Change the instruction, and ordinary people do the dangerous thing for you, in good faith, at full speed.”

In this fictional case, the town says the contractor’s remote access has been shut off, every account password has been reset, and the signal system is now cut off from the internet entirely. Engineers will have to visit each controller in person to change timings, the way they used to. The town says it is also reviewing every other system the contractor could reach from the same login.

The defence is not a sharper eye for suspicious emails. It is making sure one old password cannot rewrite what a whole town is told to do.

That advice applies well beyond one town’s traffic lights. Across Canada, small towns run water plants, street lights, and building controls on systems installed years ago, often maintained by a contractor with a single shared login. Those systems were built to be convenient, not to be defended. When one of them takes orders from the wrong person, the consequences arrive at rush hour, in the rain, at forty kilometres an hour.

Lessons Learnt

• Give remote access a second check, and an expiry date. Any account that can change a real-world system from outside should need more than a password — and a contractor’s access should switch off automatically when the job ends.
• Change shared passwords on a schedule, not after an incident. A password that has not changed in years is a password that has had years to leak. Rotate them, and keep a record of who holds each one.
• Keep the control system off the open internet. If the signals can be reached from anywhere, they can be reached by anyone. Put them on a separate network, and make changes from inside it.
• Plan for the day the lights are wrong. Decide now who posts officers, who switches the signals off, and who tells drivers what is happening. The first time you make that plan should not be in the middle of rush hour.

The fictional town says its signals are back on their normal timings, and the two people taken to hospital have been released. The lights are green and red again, in the right order. The morning they were all green at once is the part the town will not forget.

Watching the perimeter — and what slips past it.

ODTN News note: ODTN.News is a fictional news platform set within the Operation: Defend the North universe. All names, organizations, quotes, and events in this article are entirely fictitious. Any resemblance to real people, companies, or incidents is purely coincidental. The cybersecurity challenges it represents are very real.