NovoVocê sabe quais regulações se aplicam à sua empresa? Descubra em menos de 3 minutos. Nosso presente sincero:Mapeador da UEMapeador da Coreia
Como podemos ajudar?

Fale conosco em

KakaoTalkLINE

Resposta em até 48 horas

Envie-nos um e-mail →
How GPS Spoofing Affects NTP
Segurança de Rede

How GPS Spoofing Affects NTP

3 de outubro de 2026·Alex Holmquist, Panke IT Solutions LLC

On 8 July 2026, the GPS card in a Telstra stratum-1 time server in Melbourne, Australia, reset and began sending the date 2006.

Every available NTP source in Telstra's mobile core came to agree on 2006, an audit found, and some users could not make calls, including emergency calls.

That was a firmware bug. However, the stark reality is that it doesn't take a bug to reproduce the issue: GPS spoofing does the same thing on purpose.

In this blog, we explain how time errors propagate from time servers, why it's dangerous and what can stop an attack.

A GPS signal carrying the year 2006 reaches a stratum-1 server, and all six clocks below it show 2006.

Civil GPS signal carries no authentication.

Europe's Galileo has offered a signed civil signal as an operational service since July 2025, and GPS is still at the requirements stage.

In 2016, Qihoo360 researchers forged GPS and JJY time signals with low-cost parts and moved the clock of their own NTP server, 1,000 seconds at a time. Our NTP post covers what a moved clock breaks.

GPS Spoofing Protections

  • The time server can check GPS against its own oscillator. The Meinberg algorithm alarms on unexpected time steps and slow ramps and switches to holdover, using a rubidium oscillator.
  • Clients can outvote one wrong server. This NTP "majority vote" needs independent sources.

Telstra's sources all traced back to one GPS card through peering loops. That's why the bug won the majority vote on the time being 2006.

Left: three independent sources, two say 2026 and one says 2006, and the client keeps 2026. Right: three sources fed by one GPS card all say 2006, and the client accepts 2006.

How to Check Your Time Source

Run timedatectl timesync-status on Linux (chronyc tracking if the machine runs chrony) or w32tm /query /status on Windows to see the stratum and reference of what you sync to.

On 3 October 2026, we queried Korea's public NTP servers from inside Korea. Here are the results.

The KRISS (Korea Research Institute of Standards and Science) servers time.kriss.re.kr and ntp.kriss.re.kr returned stratum 3 with a private-address refid, so their upstream is hidden.

LG U+'s time.bora.net returned stratum 2. Its upstream returned stratum 1 with refid pps, a pulse-per-second reference that does not name its source.

Two chains we measured. time.kriss.re.kr and ntp.kriss.re.kr at stratum 3 point to the private address 10.248.10.100, time source unknown. time.bora.net at stratum 2 points to 123.140.16.100 at stratum 1, reference pps, pulse source unknown.

References

  1. Technology Audit Partners — Findings Report on the July 8th Telstra Outage (24 August 2026)
  2. EUSPA — From Testing to Operations: Galileo OSNMA Service Now Available to Users (5 September 2025)
  3. Hansen and Skalski (DOT) — DOT Liaisons to the GPS Enterprise (21 April 2026)
  4. SecurityWeek — NTP Servers Exposed to Long-Distance Wireless Attacks (28 May 2016)
  5. Meinberg — GNSS Spoofing and How to Mitigate It (14 April 2020)
  6. Meinberg — Messing with your Radio Time Signal (28 June 2016)
Preocupado com sua superfície de ataque?

Se quiser saber como sua infraestrutura é avaliada no modelo de varredura de um atacante, entre em contato em contact@pankeit.com para uma avaliação de superfície de ataque.

Assine nosso blog

Fique por dentro das últimas tendências de segurança

Sem spam. Cancele quando quiser.

©2026 Panke IT Solutions LLC

Austin, TX