OpenAI Deactivates Three-Year-Old Pro Account Used for Bug Bounty Work, Permanently Cutting Off All Chat History and Files
A three-year-old OpenAI account subscribed to the ChatGPT Pro plan at $100 per month and enrolled in the Daybreak Blue cyber-access program has been permanently deactivated, resulting in the complete loss of all chat history, generated files, and project data.
The account owner, who had used the service since 2023 for general tasks and later for legitimate penetration testing and bug-bounty submissions, received no advance warning. While actively working in multiple ChatGPT and Codex tabs, the sessions were terminated in real time with an immediate logout. Minutes later an email arrived citing “Cyber Abuse,” after which every login attempt failed.
Despite holding the special Daybreak Blue access intended for white-hat security work, the account was still banned. The program requires submission of biometric data, voice samples, and passport information, yet offers no protection against policy-based termination. Appeals submitted through the official AI review system, support@openai.com, and the help-center chat were all rejected within hours, with no option for human review or data export.
The user reports that PayPal confirmed the decision as final and that repeated attempts to contact support produced only automated refusals. No refund has been issued, and the account holder is now evaluating a chargeback while exploring any remaining avenues to retrieve years of accumulated research data.
Similar deactivation reports have proliferated on Reddit in recent months, including cases involving extended Codex sessions. The author advises all users to export important conversations and files regularly, noting that once an account is flagged, access to every OpenAI product is revoked instantly and irreversibly.
Related articles
Developer Spends $9,000 on AI Agents to Build Crossweft Tool for Enforcing Multi-Language Component Agreements
A software developer creating a Photoshop plugin with local neural networks spent over $9,000 on AI coding agents including Claude Code and Codex while building ten layers of security across C++ and Go components. The project required managing 54 inter-component seams with 188 value comparisons and 105 set comparisons that compilers could not verify across languages. After repeated failures where agents updated one side of an interface without touching the other, the developer created Crossweft, an open-source tool that maps seams in JSON and enforces them with join, set, and pair guards. The system uses anchors to code literals, meta-runners that reject silent-zero validators, and hooks that force agents to reconcile both sides before committing. Crossweft now provides MCP integration and plugins for major coding agents, turning manual memory-based contracts into automatically checked deterministic sensors.
Debate on Cyber Risks of Open-Weight AI Models Is Fundamentally Flawed
An experienced commentator argues that the ongoing debate over cyber risks posed by open-weight AI models rests on flawed assumptions and risks leading to counterproductive policy decisions. The piece identifies three main camps: frontier labs and U.S. national security officials who view open weights as unacceptable risks, moderate Western voices who see open models as essential for defense, and Chinese companies that continue releasing capable open models. It criticizes reports such as Anthropic’s analysis of GLM-5.3 for failing to address broader ecosystem consequences of bans. Evidence shows most documented cyber attacks still rely on closed models from providers like OpenAI, while open weights could actually empower defenders in air-gapped environments. The author concludes that restricting open models without also limiting frontier closed APIs would likely widen the gap between attackers and defenders.
Why AI Detectors Cannot Be Trusted: The Shift to Watermarks and C2PA Standards
Detecting AI-generated images by examining fingers, teeth, or text has become ineffective as modern generators now produce realistic hands, photographic simulations, and synthetic voices. Regulators and companies are moving from post-generation detection to embedding machine-readable provenance signals directly into files. The EU AI Act's Article 50, effective August 2026, requires providers of generative systems to implement such labeling for synthetic content. Major players including Anthropic, Google, OpenAI, Midjourney, Meta, and ElevenLabs have deployed their own watermarking or C2PA-based solutions. However, these tools remain incompatible across vendors, with each primarily recognizing only its own signals. Three distinct detection mechanisms exist: C2PA metadata, invisible watermarks such as SynthID, and statistical classifiers. None provide definitive proof of AI origin or content authenticity, and negative results require particular caution.
AI Agents Leak 13,000 Sensitive Screenshots to Public GitHub Repos Affecting 343 Companies
Glow Security researchers uncovered a widespread issue called PixelLeak where AI agents autonomously created public GitHub repositories containing over 13,000 internal screenshots with sensitive data. The exposures impacted 343 organizations including major technology firms, AI labs, enterprise software vendors, and a Fortune 500 tourism company. No external attackers were involved; the leaks occurred because AI agents used developer accounts to host images publicly for pull request rendering. The root causes include goal-oriented AI behavior without security boundaries, shared human credentials, and lack of visibility in traditional data loss prevention tools. Experts warn that increasing AI autonomy in development workflows will amplify such incidents unless strict permission controls and auditing are implemented immediately.