Missleading warning message: "Your account was flagged for potentially high-risk cyber activity ..."

Resolved 💬 17 comments Opened Feb 17, 2026 by bfroemel Closed Feb 19, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

main branch, #02e9006547

What subscription do you have?

none

Which model were you using?

_No response_

What platform is your computer?

_No response_

What terminal emulator and version are you using (if applicable)?

_No response_

What issue are you seeing?

If the model name doesn't match the slug the warning introduced by https://github.com/openai/codex/pull/11964 is emitted:

⚠ Your account was flagged for potentially high-risk cyber activity and this request was routed to gpt-5.2 as a fallback. To regain access to gpt-5.3-codex, apply for

trusted access: https://chatgpt.com/cyber or learn more: https://developers.openai.com/codex/concepts/cyber-safety

What steps can reproduce the bug?

Use of codex with other models where model name does not match slug.

What is the expected behavior?

The warning is good, but I would not necessarily conclude that an "account was flagged". (For example, I have none and just use codex with other models).

Maybe consider to warn only about the routing situation, explaining that requests are routed to a model with a name that is different than the configured model. The warning should mention which model is used and what model was configured.

Besides: the current warning message contains static model names and would be outdated soon.

Thanks!

Additional information

_No response_

View original on GitHub ↗

17 Comments

etraut-openai contributor · 5 months ago

Thanks for the bug report. Can you provide more details about how you've configured your model provider? A snippet from your config.toml would be most helpful. That will help us repro the problem. Is this a local model like gpt-oss-120b? Thanks!

bfroemel · 5 months ago

Yes, I encountered the warning while using codex with a custom provider where indeed there was a name/slug mismatch.

conig.toml:

model_provider = "openai-responses"
model = "gpt-oss"

[model_providers.openai-responses]
name = "internal"
base_url = "**REDACTED**"
wire_api = "responses"

[features]
remote_models = true

models json descriptor:

    {
      "supports_reasoning_summaries": false,
      "support_verbosity": false,
      "default_verbosity": null,
      "apply_patch_tool_type": "function",
      "input_modalities": [
        "text"
      ],
      "truncation_policy": {
        "mode": "bytes",
        "limit": 10000
      },
      "supports_parallel_tool_calls": false,
      "context_window": 96000,
      "reasoning_summary_format": "none",
      "slug": "gpt-oss",
      "display_name": "gpt-oss",
.
.
.

The problematic message is produced here: https://github.com/openai/codex/blob/5c75aa7b89a70bc2cc410a6fd238749306ec4c5e/codex-rs/core/src/codex.rs#L2565-L2581

/edit: corrected link to problematic source code

etraut-openai contributor · 5 months ago

OK, thanks. Very helpful!

iharc-jordan · 5 months ago

I am also getting this warning despite being verified.

etraut-openai contributor · 5 months ago

@iharc-jordan, are you using a custom model provider like the OP in this thread? Or are you trying to use gpt-5.3-codex with the default openai model provider?

catap · 5 months ago

@etraut-openai I've tried 0.102.0 version and I use gpt-5.2-xhigh, not codex model and not 5.3. I do have serveral:

⚠ Your account was flagged for potentially high-risk cyber activity and this request was routed to gpt-5.2 as a fallback. To regain access to gpt-5.3-codex, apply for trusted access: https://chatgpt.com/cyber or learn more: https://developers.openai.com/codex/concepts/cyber-safety

and I had passed KYC, but it still flagged that.

Before update to 0.102.0 I never saw that message.

iharc-jordan · 5 months ago
@iharc-jordan, are you using a custom model provider like the OP in this thread? Or are you trying to use gpt-5.3-codex with the default openai model provider?

My bad, this is a default model. I was actually using 5.2 non codex when I got the flag

Fangzhou66 · 5 months ago

I got the same issue, I am using 5.2-pro with api key and url https://us.api.openai.com/v1

AidenNovak · 5 months ago

I got the issue and i am using 5.3-codex-xhigh,please help with the fixing , job needs to be done while i actually have some trouble now , please

etraut-openai contributor · 5 months ago

If you're not using gpt-5.3-codex and are seeing this message, that's a bug. You can ignore the message. We're working on a fix for this.

a2975667 · 5 months ago

I also received this warning after upgrading to codex-cli 0.103.0 and the requested work was "downgraded to codex-5.2"; but I was able to reselect the model on a different task. Using my team account.

mudcube · 5 months ago

You could try deleting ~/.codex and reinstalling—seems like a clean reset sometimes fixes this.

mudcube · 5 months ago

I take it back, installing version 0.101.0 works for me though.

winoros · 5 months ago

Seems that I'm in the same situation. I got the warning when I was using 5.2 xhigh. But I didn't see it if I was using 5.3codex xhigh.

ccmvn · 5 months ago

Using CLI 0.104.0 on Windows. My account was flagged and I cannot complete verification at https://chatgpt.com/cyber. Verification succeeds but immediately restarts 019c7046-7e87-72a0-b448-473c7833fd2c

tiagonrodrigues · 5 months ago

"Using CLI 0.104.0 on Windows. My account was flagged and I cannot complete verification at https://chatgpt.com/cyber."

Same here. Tried every doc to verify.

bfroemel · 5 months ago

My issue (related to custom providers when not returning a model name that exactly matches slug) is fixed by https://github.com/openai/codex/pull/12061

Instead of using the responses API model name, it uses a HTTP header (OpenAI-Model/X-OpenAI-Model). If that header is missing (usually the case with custom providers) the whole check is never made thus the warning isn't emitted anymore.

Closing this; if anyone still has issues please open a new issue and/or track one of the others related to the official codex model providers: https://github.com/openai/codex/issues?q=state%3Aopen%20label%3A%22safety-check%22

Thanks!