
The information displayed in the AIM should not be reported as representing the official views of the OECD or of its member countries.
Proton's CEO mandated a rapid shift to AI-assisted software development, halting traditional developer hiring by 2026. Internal pressure to prioritize AI-generated code over security led to increased vulnerabilities, sparking user backlash and employee concerns about job security and software safety. The incident centers on realized harm from insecure AI-generated code.[AI generated]
Why's our monitor labelling this an incident or hazard?
The article explicitly involves AI systems (large language models) used to generate production code. The company's internal policy prioritizes speed over security, leading to a high incidence of vulnerabilities in AI-generated code, as supported by cited studies showing 87% of AI-generated pull requests contain exploitable flaws. This directly threatens user security and privacy, which are fundamental rights and core to Proton's service promise. The AI system's use and the company's operational decisions have directly contributed to this harm. Although no specific breach is reported, the ongoing deployment of vulnerable code constitutes realized harm to users and communities, fitting the definition of an AI Incident. The article also discusses the broader ecosystem impact and internal controversies, but the central issue is the direct harm linked to AI-assisted software development practices at Proton.[AI generated]