Other
Operation Aurora β Chinese APT Nation-State Espionage (Google, Adobe, 30+ Companies)
Primary Source βIncident Details
Operation Aurora was a sophisticated, coordinated nation-state cyber espionage campaign originating in China and targeting at least 30 major corporations, with Google being the most prominent. The campaign began as early as mid-2009 and was discovered in late December 2009. Google publicly disclosed the attack on January 12, 2010, in a landmark blog post, naming China and threatening to exit the Chinese market. The attack exploited a zero-day IE vulnerability (CVE-2010-0249) via spear-phishing. At Google, attackers stole source code and accessed Gmail accounts of Chinese human rights activists β the latter purpose suggesting intelligence, not just IP theft. Other confirmed targets included Adobe Systems, Juniper Networks, Akamai, Yahoo, Symantec, Northrop Grumman, Morgan Stanley, and Dow Chemical. The campaign was attributed by McAfee and multiple intelligence agencies to Elderwood Group (also tracked as APT17, APT9, or Comment Crew) β a Chinese PLA-affiliated threat actor. The name ‘Aurora’ came from a file path in the malware (‘aurora’ appeared in the attacker’s C2 infrastructure). Operation Aurora marked a watershed moment: it was the first time a major US corporation publicly named a nation-state (China) as responsible for a cyberattack, triggering significant diplomatic fallout and fundamentally shifting corporate attitudes toward nation-state cyber threats. The US-China diplomatic tension over Aurora was a precursor to the broader APT campaign disclosures that followed throughout the 2010s.
Technical Details
- Initial Attack Vector
- Spear-phishing emails delivering a zero-day exploit for Internet Explorer (CVE-2010-0249, a use-after-free vulnerability in IE 6/7/8); watering hole attacks; lateral movement and data exfiltration once initial foothold established
- Vendor / Product
- Microsoft Internet Explorer 6/7/8
- Malware Family
- Hydraq (Aurora backdoor)
- CVE / GHSA References
- CVE-2010-0249
Timeline
- 2009-06-01 Breach occurred
- 2010-01-12 Publicly disclosed