OpenAI co-founder Sam Altman’s home was attacked with a Molotov cocktail; the suspect has been arrested

Gate News message, April 11, an OpenAI spokesperson confirmed that the San Francisco Police Department arrested a suspect earlier on Friday. The suspect allegedly threw a Molotov cocktail at the residence of OpenAI founder and CEO Sam Altman and carried out threatening behavior outside OpenAI’s San Francisco headquarters. OpenAI said: “Fortunately, no one was injured. We’re very grateful that the San Francisco Police Department was able to respond so quickly, and we also appreciate the support provided by the city government in helping ensure our employees’ safety. The suspect has been taken into custody, and we are assisting the police with their investigation.” The San Francisco Police Department said that earlier on Friday, officers responded to a residence in San Francisco’s North Beach neighborhood to conduct an arson investigation. After the suspect fled on foot, police received a call and rushed to a business at 1400 Third Street to address an incident involving a man threatening to burn down a building. After arriving at the scene, officers recognized the man as the same suspect and arrested him. It is reported that the suspect is a 20-year-old man. At present, Altman has not yet issued a public statement regarding the incident.

Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
No comments