← Breach analysis by the Dual Vulnerabilities framework

Indian Navy Eastern Command data theft (Suspected Chinese hackers, 2012)

2012 · India · O - Public administration and defence · Data theft via malware-infected USB drives bridging air-gapped naval computers

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft via malware-infected USB drives bridging air-gapped naval computers

Dual vulnerability type

Strategy to Execution

Evidence coverage: 2/6 stages, weight 11/60

Decisive stage: entry (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) Strategic expectation: the Indian Navy held formal, specific rules for its crown-jewel data - pen drives prohibited in naval offices, and sensitive data stored only on standalone computers not connected to the Internet, which were not supposed to have ports or access points for external storage. (2) In practice: prohibited pen drives carrying a virus were used to transfer data between those standalone machines at Eastern Naval Command HQ; the malware cached confidential files, moved them via USB to Internet-connected PCs and relayed them to Chinese IP addresses; the Navy's own Board of Inquiry indicted at least six mid-level officers for procedural lapses, and the detection came only via an external intelligence input from November 2011, months earlier than the Navy's own discovery. (3) This is a Strategy to Execution gap, resting on the entry stage: the doctrinal artefact existed and was precise, yet it did not translate into operational reality - media controls that the ban assumed (blocked ports, enforced no-media rules) were not realised on the floor, and individual officers' repeated non-compliance shows the policy lived on paper only. Nothing in the sources shows leadership deferring or under-resourcing the ban, so the break is execution, not leadership; the detection gap points secondarily to Expertise to Execution but rests on inference and never wins the tie-break. The entry vector's technique (USB malware) is not the basis of the type - the basis is the documented gap between the Navy's own prohibition and its practice. RM11 (Strategy to Execution lens): the specific existing procedure - pen drives prohibited in naval offices, standalone machines kept portless - was never translated into enforced routines or configurations, with the Board of Inquiry's finding of officers' procedural lapses as the evidence of non-compliance (causal role: Perpetuating). RM25 (Strategy to Execution lens): media-handling requirements for portable devices were not implemented - infected pen drives were carried onto the command and used to bridge air-gapped computers, which is what made the intrusion possible (causal role: Enabling). RM34 (Strategy to Execution lens): the monitoring and detection requirement on a sensitive command network was not operated as intended - the infection persisted after a November 2011 intelligence input before an expert board of inquiry found it, so the intrusion stayed hidden from the victim's own monitoring (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

Source caveats: the dataset's source_url (archive.indianexpress.com) no longer resolves (connection failed); cited instead is the Wayback snapshot opened during this analysis. Attribution to China rests on traced IP addresses and unnamed Indian officials (receiver attribution via media); no forensic or official report confirms the actor - this does not lower confidence, as the DV rests on victim-side evidence. Reported data loss is contradictory: Indian Express sources say classified data was leaked, while the defence minister's Lok Sabha statement (via Rediff) says not much damage took place and no sensitive information went out; EuRepoC scores the theft at the lowest intensity tier. Rediff also reports an earlier, separate Indian Navy incident of officers deliberately leaking information; it is not a comparable technical weakness, so no recurring-weakness marker is coded. Recovery and disruption were not in play (no outage reported). Incident disclosed by media, not by the Navy (EuRepoC source_disclosure).