Tuesday, February 11, 2025
Homecyber securityU.S. Senator Blasts Microsoft for Chinese Hack Seeks Federal Action

U.S. Senator Blasts Microsoft for Chinese Hack Seeks Federal Action

Published on

SIEM as a Service

Follow Us on Google News

A joint alert from the FBI and CISA concerning a hacking campaign that targeted Microsoft customers, including government entities, was released on July 12.

In a letter to the directors of the Department of Justice, Federal Trade Commission (FTC), and Cybersecurity and Infrastructure Security Agency (CISA), U.S. Senator Ron Wyden stated that Microsoft “bears significant responsibility for this new incident.”

Microsoft is held accountable for its poor cybersecurity procedures, which let China carry out a successful espionage campaign against the US government, reads the letter sent by Senator.

An Overview of the Chinese Hack

Press sources claim that “at least hundreds of thousands of individual U.S. government emails” were taken, and that the email accounts of the secretary of commerce, the ambassador of the United States to China, and the assistant secretary of state for East Asia were among those that were affected.

According to Microsoft, the breach happened as a result of hackers obtaining an encryption key that the company had created for its identification service, Microsoft Account (MSA).

Microsoft made another mistake, which led to the theft of government emails. Although the encryption key was for consumer accounts, “a validation error in Microsoft code” allowed the hackers to access accounts for government agencies and other organizations that were hosted by Microsoft by making fake tokens for such accounts.

Wyden’s List OfMicrosoft’sCybersecurity Flaws

First, according to Wyden’s letter, Microsoft shouldn’t have had a single skeleton key that, in the event of theft, might be used to get access to various customers’ private conversations.

Secondly, he said, high-value encryption keys should be kept in an HSM, whose main purpose is to prevent encryption key theft, as Microsoft noted in a recent SolarWinds incident.

Third, the encryption key that was utilized in this most recent attack was made by Microsoft in 2016 and it expired in 2021.

As a final point, although Microsoft’s engineers shouldn’t have released systems that broke such fundamental cybersecurity rules, Microsoft’s internal and external security audits ought to have discovered these issues, he said.

“These flaws were not detected raises questions about what other serious cybersecurity defects these auditors also missed”, he said.

“While Microsoft certainly deserves most of the blame, the executive branch also bears responsibility”.

Wyden asked for many investigations to look into why Microsoft neglected its security recommendations.

Additionally, he urges directors to take all necessary actions to hold the business accountable for any violations of that orders.

Keep yourself informed about the latest Cyber Security News by following us on GoogleNews, Linkedin, Twitter, and Facebook.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Hackers Exploit Valentine’s Day Domains for Sneaky Cyber Attacks

Cybercriminals are capitalizing on the season of love to launch sneaky and deceptive cyberattacks.According...

EARLYCROW: Detecting APT Malware Command and Control Activities Over HTTPS

Advanced Persistent Threats (APTs) represent a sophisticated and stealthy category of cyberattacks targeting critical...

Enhanced IllusionCAPTCHA: Advanced Protection Against AI-Powered CAPTCHA Attacks

As AI technologies continue to evolve, traditional CAPTCHA systems face increasing vulnerabilities.Recent studies...

Akira Ransomware Dominates January 2025 as the Most Active Ransomware Threat

January 2025 marked a pivotal month in the ransomware landscape, with Akira emerging as...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Hackers Exploit Valentine’s Day Domains for Sneaky Cyber Attacks

Cybercriminals are capitalizing on the season of love to launch sneaky and deceptive cyberattacks.According...

EARLYCROW: Detecting APT Malware Command and Control Activities Over HTTPS

Advanced Persistent Threats (APTs) represent a sophisticated and stealthy category of cyberattacks targeting critical...

Enhanced IllusionCAPTCHA: Advanced Protection Against AI-Powered CAPTCHA Attacks

As AI technologies continue to evolve, traditional CAPTCHA systems face increasing vulnerabilities.Recent studies...