False positive cyber-safety routing. gpt-5.3-codex usage

Resolved 💬 2 comments Opened Feb 18, 2026 by Daimon04 Closed Feb 20, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Context: I’m a software engineer using Codex CLI for legitimate development work. I ran the ai-factory skill ($ai-factory) from https://github.com/lee-to/ai-factory on a work repository to generate project tasks/docs.

What happened: After running $ai-factory, every Codex CLI request shows:
"Your account was flagged for potentially high-risk cyber activity and this request was routed to gpt-5.2 as a fallback..."

I did not request or perform offensive security, exploitation, malware, phishing, credential theft, or any unauthorized scanning. This was a defensive/engineering workflow (project automation / codebase review). Please review and remove the flag or advise what to change to avoid triggering it.

Time (local): 2026-02-18 16:25 (MSK)
Environment: codex-cli on macOS
Repo type: internal work repo (can’t share code)
Skill invoked: $ai-factory

Thread: 019c70f2-2ee8-7bc0-a256-cb17638af079

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 6 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #12136
  • #12132
  • #12130
  • #12127
  • #12125

Powered by Codex Action

etraut-openai contributor · 6 months ago

Thanks for the bug report. We're continuing to tune our cyber safety classifiers to make them more accurate. You can read more about this here. If you see this again in the future and believe it's a false positive (i.e. you aren't doing anything related to cybersecurity), please use the /feedback slash command and choose "Safety Check" to report it. That will help us further tune our checks.