maborak.com~/blog/openrouter-gmi-cloud-exposuresoftware & infrastructure engineering
Back to all articles

OpenRouter’s GMI Cloud notice: which prompts to review

Overview

Use OpenRouter’s request logs to review prompts routed to GMI Cloud during the notice window, then revoke exposed credentials and verify the cutover.

OpenRouter says (opens in a new tab) it removed three inference providers from its platform and notified potentially affected customers. In a customer notice, OpenRouter says it disabled all GMI Cloud endpoints on 20 November and asks recipients to review requests routed there from 18 October through 18 November 2026. If you know a live credential was in one of those prompts, revoke or rotate it now.

Checked 22 November 2026.

Background

The customer notice says GMI Cloud reported unauthorized access on 21 and 22 October and again from 27 October. GMI Cloud told OpenRouter that the attacker searched the retained prompts for credentials. The notice says GMI Cloud revoked two compromised credentials on 18 November and had seen no attacker access after 17 November.

OpenRouter set 18 October as the start of the review window because the system reportedly kept about three days of request content for troubleshooting. The public announcement (opens in a new tab) does not name GMI Cloud or confirm those dates.

Mechanics

The model name in an OpenRouter request does not tell you which provider received the prompt. OpenRouter can route the same model to different providers (opens in a new tab), and it can try another provider if the first returns an error.

Requested model → OpenRouter routing → provider endpoint

Start in OpenRouter Logs (opens in a new tab). Use the dates in your notice to narrow the results, then check the final provider and any recorded fallback attempts. If older records are missing or show only the final provider, ask OpenRouter support (opens in a new tab) for the affected request IDs and the exact cutoff times.

Impact

The notice covers requests sent to any GMI Cloud model within the stated dates. A matching record tells you which prompt to review. It does not tell you whether anyone read it. Dragos researcher HD Moore (opens in a new tab) observed AWS calls made with test keys he had placed in prompts. His public report leaves the providers unnamed and does not establish that a customer’s keys were used.

Probe

We ran the following in a shell on macOS 27.0.1 with Python 3.15.2. The dates in the notice do not specify a timezone, so the fixtures use UTC midnights to exercise the boundaries. The inputs are normalized metadata for one synthetic model; the script does not read prompts, query OpenRouter, or account for unrecorded fallback attempts.

python3 - <<'PY'
from datetime import datetime, timezone
from platform import mac_ver, python_version

def classify(provider, created_at, target, start, stop):
    if provider and provider != target:
        return "other-provider"
    try:
        timestamp = datetime.fromisoformat(created_at.replace("Z", "+00:00"))
    except (AttributeError, ValueError):
        return "unknown-time"
    if timestamp.utcoffset() is None:
        return "unknown-time"
    if not start <= timestamp < stop:
        return "outside-window"
    return "review-prompt" if provider else "unknown-provider"

start = datetime(2026, 10, 18, tzinfo=timezone.utc)
stop = datetime(2026, 11, 19, tzinfo=timezone.utc)
gmi = "GMI Cloud"
fixtures = [
    ("before-start", gmi, "2026-10-17T23:59:59Z", "outside-window"),
    ("start", gmi, "2026-10-18T00:00:00Z", "review-prompt"),
    ("end-date", gmi, "2026-11-18T23:59:59Z", "review-prompt"),
    ("after-end", gmi, "2026-11-19T00:00:00Z", "outside-window"),
    ("other-provider", "Fixture Provider", "2026-10-18T00:00:00Z", "other-provider"),
    ("missing-provider", None, "2026-10-18T00:00:00Z", "unknown-provider"),
    ("missing-time", gmi, None, "unknown-time"),
    ("missing-offset", gmi, "2026-10-18T00:00:00", "unknown-time"),
    ("offset-boundary", gmi, "2026-10-17T20:00:00-04:00", "review-prompt"),
]
print(f"macOS {mac_ver()[0]}; Python {python_version()}")
for name, provider, created_at, expected in fixtures:
    result = classify(provider, created_at, gmi, start, stop)
    if result != expected:
        raise SystemExit(f"{name}: expected {expected}, got {result}")
    print(f"{name}: {result}")
PY

The filter marked the GMI Cloud request at midnight UTC on 18 October for review. It returned other-provider for the same model and time on a different provider, and unknown-provider when the provider was missing.

Provider and date filter output (9 fixture rows)
macOS 27.0.1; Python 3.15.2
before-start: outside-window
start: review-prompt
end-date: review-prompt
after-end: outside-window
other-provider: other-provider
missing-provider: unknown-provider
missing-time: unknown-time
missing-offset: unknown-time
offset-boundary: review-prompt

Mitigation

Review the original prompt content in your own application records. The notice recommends starting with the most privileged secrets. If a prompt contained an AWS IAM access key, deactivate the old key promptly (opens in a new tab) and restore the workload with a replacement credential. Check already-issued AWS sessions (opens in a new tab) separately. Remove the secret from any prompt template or log excerpt before reusing that text.

Verification

Check that IAM (opens in a new tab) shows the old key as inactive. From the running workload, run aws sts get-caller-identity (opens in a new tab) using its normal credential chain. Confirm the expected account and principal, then verify that a normal application operation succeeds.

Two keys for the same IAM user return the same identity. Use CloudTrail’s userIdentity.accessKeyId (opens in a new tab) to check that a direct IAM-user call used the replacement key. For an assumed role, check the session and its issuer instead.

Search for old-key activity in the relevant AWS accounts and Regions. CloudTrail Event History (opens in a new tab) covers 90 days of management events per Region. To check data events, consult a trail or event data store that was configured to collect them.

Sources

Customer notice

OpenRouter, private GMI Cloud customer notice, November 2026. The notice is the source for the reported access, retention, shutdown date and dates customers were asked to review. Cited with the recipient’s permission. There is no public URL, and account details are omitted.

Back to all articles

Technologies we work with

  • Argo CD
  • Kubernetes
  • Docker
  • Podman
  • Ansible
  • Jenkins
  • Chef
  • Proxmox VE
  • Google Cloud
  • Linux
  • Red Hat
  • CentOS
  • NGINX
  • Apache
  • Traefik
  • Prometheus
  • Grafana
  • PostgreSQL
  • MySQL
  • MariaDB
  • Redis
  • etcd
  • Qdrant
  • Elasticsearch
  • Logstash
  • Kibana
  • PagerDuty
  • Go
  • Python
  • FastAPI
  • PHP
  • TypeScript
  • React