Third-party relay offers Codex and Claude Code in unsupported markets

Key points

• A third-party relay supplies access to Codex and Claude Code where vendors do not sell.
• The service reportedly disables sandboxing and other safeguards.
• Users face containment, compliance, and support risks.
• No CVE is assigned; this is a policy and configuration issue, not a software flaw.

A third-party relay operator is advertising access to OpenAI’s Codex and Anthropic’s Claude Code for developers in mainland China and other locations where those vendors do not offer service. The arrangement is not an official integration; it routes users around regional sales restrictions and vendor-supported onboarding.

According to the facts, the relay provides the coding tools while switching off sandbox protections and disabling security features. That matters because coding agents can read files, run commands, and reach networks. Sandboxing is a primary containment layer; removing it increases the chance that a compromised or misconfigured agent affects the host or local data.

The people affected are developers and organizations using the relay, plus IT teams responsible for endpoints and procurement. They may get functionality without vendor support, patching, or terms-of-service coverage. Vendors also lose visibility into how their products are being used, and organizations may violate licensing or regional policy.

Context: this is not a CVE-backed vulnerability. It is an access and configuration problem. The severity hint is informational, but the operational risk rises when users disable safeguards to make an unsupported path work. Watch for relay domains, proxy configurations, API keys issued outside approved channels, and local settings that turn off sandboxing.

IT admins should treat unsupported relays as shadow IT. Confirm whether staff use Codex or Claude Code through third parties, block unapproved endpoints, and require vendor-supported access. Audit agent configurations for disabled sandboxing, review egress logs, and remind developers not to trade containment for convenience.

What to do now

1. Inventory all Codex and Claude Code usage, including third-party relay or proxy endpoints, and identify the owning teams.
2. Block unapproved relay domains and proxy routes at DNS, firewall, and web gateway layers.
3. Enforce procurement through vendor-supported channels and deny access paths that bypass regional sales limits.
4. Audit local and CI configurations for disabled sandboxing or turned-off security features, then restore secure defaults.
5. Monitor egress and API logs for relay traffic and non-approved keys; rotate any exposed credentials.
6. Publish a clear developer policy prohibiting third-party relays and disabling safeguards for convenience.
7. Review vendor terms and legal or compliance exposure, and document any approved exceptions.

Original source

Dark Reading