OpenAI

Company

Last mentioned: 1h ago

Timeline

  1. Threat Detection

    OpenAI safety systems flag ChatGPT interactions indicating a potential school shooting threat.

  2. Internal Deliberation

    OpenAI teams discuss the ethical and legal implications of alerting Canadian authorities.

  3. Public Disclosure

    Reports surface that OpenAI considered alerting police months before the suspect's actions became public knowledge.

  4. Industry Integration

    Security researchers and developers begin benchmarking existing LLMs against the EVMbench dataset.

  5. EVMbench Launch

    OpenAI and Paradigm officially announce the release of the EVMbench framework for AI agent evaluation.

Stories mentioning OpenAI 3

security Bearish

OpenAI Faces Scrutiny Over Failure to Report Mass Shooter's Chatbot Logs

OpenAI is under intense pressure following revelations that it failed to alert law enforcement about threatening chatbot interactions with a mass shooter prior to an attack. Despite possessing logs indicating violent intent, the company reportedly did not disclose this information to the RCMP until after the tragedy occurred.

6 sources
Regulation Bearish

OpenAI's Deliberation Over Canadian Shooting Threat Sparks AI Safety Debate

OpenAI reportedly identified a potential school shooting suspect through ChatGPT interactions months before an incident but faced internal deliberations regarding alerting Canadian authorities. The revelation highlights the growing tension between AI user privacy and the corporate responsibility to prevent real-world violence.

2 sources
security Bullish

OpenAI and Paradigm Launch EVMbench to Test AI-Driven Smart Contract Auditing

OpenAI and crypto venture firm Paradigm have introduced EVMbench, an evaluation framework designed to measure the proficiency of AI agents in identifying and remediating vulnerabilities within Ethereum smart contracts. This collaboration marks a significant step toward automating the auditing process for decentralized applications, potentially reducing the frequency of high-profile DeFi exploits.

2 sources