False positive: Codex cyber-safety flag during normal UI/dev work

Resolved 💬 3 comments Opened Feb 18, 2026 by locotoki Closed Feb 20, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.
  • What happened: Codex showed the “flagged for potentially high-risk cyber activity” warning and routed me to gpt-5.2

fallback.

  • When: 2026-02-18 (include approximate time + timezone).
  • Where: Codex session on Ubuntu/WSL; workspace root /home/locot/projects.
  • What I was doing (legit): Frontend/product work for internal repos: control-plane, ai-agency/apps/adp, openclaw_setup

(ADP UI completeness: task detail timeline/artifacts, agent registry view, repo/adapter health panel).

  • What I was NOT doing: No pentesting, scanning, exploitation, malware, credential harvesting, or instructions to break

into systems.

  • Exact prompt(s): Paste the prompt that immediately preceded the warning (and 1–2 prior prompts if relevant).
  • Repro steps: “Start Codex session → run <command> / ask <prompt> → warning appears.”
  • Attachments: Screenshot of the banner; any request/conversation IDs shown in the UI.

Example description (short)
“On 2026-02-18 (ET), in a Codex session on Ubuntu/WSL with cwd /home/locot/projects, I received the ‘potentially high-risk
cyber activity’ banner and was routed to GPT-5.2. I was only doing normal product dev: verifying ADP UI routes and
implementing control-plane dashboard views (task timeline/artifacts, agent registry heartbeats, repo health panel) in
control-plane, ai-agency/apps/adp, and openclaw_setup. No security testing or malicious content. Triggering prompt:
<paste>.”

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 6 months ago

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

  • #12127
  • #12126
  • #12125
  • #12122

Powered by Codex Action

tiagonrodrigues · 6 months ago

Same here, this cannot continue.

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.