en.wikipedia.org/wiki/Dmitri_Alperovitch
3 corrections found
Silverado Policy Accelerator launched in March 2021
Silverado says it officially launched in February 2021, not March 2021.
Full reasoning
Silverado’s own website contradicts this date. Its official history page says, "Silverado officially launched in February 2021." Silverado also marked February 23, 2022 as the first anniversary of its public launch, which places the launch in February 2021, not March 2021.
2 sources
- Silverado History
History Introduction Silverado officially launched in February 2021...
- Celebrating Silverado Policy Accelerator's First Year
Published by: Silverado Policy Accelerator • Feb 23, 2022 ... Today marks the first anniversary of Silverado Policy Accelerator's public launch.
and traced them to Song Zhiyue, a Chinese national living in Heze City, Shandong.
McAfee’s Night Dragon report did not say the attacks were traced to Song Zhiyue as an identified perpetrator.
Full reasoning
The primary McAfee report is more limited than this sentence suggests. In Appendix B, McAfee says it had "no direct evidence to name the originators of these attacks" and only identified one individual who provided crucial command-and-control infrastructure in Heze City, Shandong. McAfee explicitly added that it did not believe this person was the mastermind behind the attacks. Contemporary reporting on the report likewise says McAfee identified a man in Heze who provided servers used in the operation, not that the operation itself was conclusively traced to him as the attacker.
So this wording overstates the evidence: Song Zhiyue was described as a provider of infrastructure tied to the operation, not as the person to whom the Night Dragon attacks were definitively traced.
2 sources
- Global Energy Cyberattacks: “Night Dragon” (McAfee white paper)
McAfee has no direct evidence to name the originators of these attacks... we have been able to identify one individual who has provided the crucial C&C infrastructure... Although we don’t believe this individual is the mastermind behind these attacks...
- Hackers in China hit Western oil firms - Taipei Times
McAfee said it identified an individual in Heze, Shandong Province, who provided servers that hosted an application that controlled computers at the victim companies. The report did not identify the man, but US news reports citing McAfee gave his name as Song Zhiyue.
The review discovered that Storm-0558 broke into Microsoft's corporate network and stole a cryptographic key used for signing authentication tokens for accessing customer email accounts.
The review did not conclusively determine how or when Storm-0558 obtained the signing key.
Full reasoning
This sentence states a disputed causal chain as if the CSRB review established it as fact. But reporting on Microsoft’s own investigation and on the CSRB report says the key-acquisition mechanism was not conclusively determined.
TechCrunch reported that Microsoft said Storm-0558 had compromised a Microsoft engineer’s corporate account and that this was the "most probable mechanism" for how the key was obtained, but Microsoft also said it "cannot be completely certain" because it lacked logs showing the exfiltration.
Coverage of the CSRB report quotes the board as saying that, as of the date of the report, Microsoft did not know how or when Storm-0558 obtained the signing key. In other words, the review did not definitively establish that Storm-0558 broke into Microsoft’s corporate network and stole the key in the way this sentence presents. That may have been a leading theory, but it was not a confirmed finding.
2 sources
- Microsoft reveals how hackers stole its email signing key... kind of | TechCrunch
Microsoft said it cannot be completely certain this was how the key was stolen because "we don't have logs with specific evidence of this exfiltration," but said this was the "most probable mechanism by which the actor acquired the key."
- Microsoft's lax security blasted by investigators after serious breach
In fact, said CSRB "As of the date of this report, Microsoft does not know how or when Storm-0558 obtained the signing key."