Ten years. Not a typo.
Velvet Ant — a PRC-linked cyberespionage cluster tracked by Sygnia — maintained covert access to a large organization's air-gapped critical infrastructure network for a full decade by hijacking the authentication stack itself. Sygnia is calling it Operation Highland. This is not a breach story. It's a doctrine story.
The air gap didn't fail. The thing that crosses the air gap did. Every isolated network has a seam — a jump server, an authentication relay, an admin workstation that touches both sides. Velvet Ant found that seam in 2016 and lived in it for ten years. The lesson isn't that air gaps are useless. The lesson is that an air gap is only as strong as its weakest bridging point. That's a subtler and harder problem.
Compromise a single endpoint, you see that endpoint. Compromise the auth flow, you see everything that authenticates — every admin session, every privileged operation, every credential rotation. You become the shadow administrator. You can watch for a decade and never need to escalate privileges because you already have them by proxy. The article states it directly: "full visibility into administrative activity." Ten years of it.
Velvet Ant's toolchain preference is worth tracking as a pattern in its own right. F5 BIG-IP in 2024 — three years undetected before Sygnia caught them. Cisco NX-OS zero-day in 2024. Internet-facing systems as initial access here. This is a deliberate doctrine, not opportunism. Network appliances run custom firmware, rarely carry EDR, have long patch cycles, and are trusted by design. They are invisible to most endpoint detection stacks. Three campaigns, same playbook. We are nothing if not consistent — though in this case it's the attacker demonstrating the consistency.
Ten years is not an anomaly. It's the goal. Nation-state espionage isn't ransomware. The objective isn't disruption; it's sustained collection. A decade of visibility into a critical infrastructure operator's administrative activity means ten years of configuration data, personnel changes, operational patterns, vulnerability windows, and contingency plans. If this was an energy or water utility — Sygnia hasn't named the organization — that's a decade of building the playbook for a future destructive operation. The access gets remediated. The knowledge doesn't.
Detection failed because the attacker was the authentication system. Traditional detection looks for anomalies against a baseline. When the attacker controls the auth layer, they control what looks normal. Every SIEM alert, every log, every access record passed through infrastructure they could see and potentially manipulate. This is the specific detection gap Operation Highland exposes: behavioral analytics on authentication infrastructure itself, not just endpoint telemetry. Most enterprise security programs invest heavily in perimeter and endpoint. Authentication infrastructure — RADIUS servers, TACACS , SSO relays, jump server session brokers — receives a fraction of that scrutiny, runs older software, and is implicitly trusted by every detection system downstream of it. That asymmetry is what a decade of silence looks like.
MITRE mapping for the record: T1190 (initial access via public-facing application), T1556 (modify authentication process — the core technique), T1078 (valid accounts leveraged from the compromised auth stack), T1599 (network boundary bridging, internet-connected to air-gapped), T1021 (remote services for lateral movement post-pivot), T1560 (systematic data staging across ten years of collection), T1070 (indicator removal — ten years undetected implies active artifact manipulation, not just luck).
The risk read: this is a template, not an isolated incident. Velvet Ant has now been documented across F5, Cisco, and unnamed critical infrastructure targets with the same underlying logic. Any organization running internet-facing network appliances as the boundary of a sensitive internal network should treat this as an active threat model. And whatever this unnamed organization does, their adversary now knows them better than they know themselves. That's not a patch problem. That's a strategic exposure that persists well after remediation.
CVE-2026-41940 is the associated auth bypass. Full details at NVD.
BleepingComputer, June 13, 2026.